Systems and methods for rendering weblinks inside a remote application using an embedded browser

ABSTRACT

Embodiments described include systems and methods for providing a preview for a link in a network application. A client application operating on a client device provides access to a network application. The client application includes an embedded browser for accessing the network application. The embedded browser displays a link within a user interface for the network application. When a user provides a user action on the link, a preview engine for the embedded browser detects the user action. The preview engine provides a preview of the link by rendering a preview in a preview region of the embedded browser.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to and thebenefit of U.S. patent application Ser. No. 16/138,598, titled “SYSTEMSAND METHODS FOR RENDERING WEBLINKS INSIDE A REMOTE APPLICATION USING ANEMBEDDED BROWSER,” and filed on Sep. 21, 2018, the contents of all ofwhich are hereby incorporated herein by reference in its entirety forall purposes.

FIELD OF THE DISCLOSURE

The present application generally relates to management of applications,including but not limited to systems and methods for previewing linkswithin remotely provisioned applications using an embedded browser.

BACKGROUND

As the workforce of an enterprise becomes more mobile and work undervarious conditions, an individual can use one or more client devices,including personal devices, to access network resources such as webapplications. Due to differences between the client devices and themanner in which network resources can be accessed, there are significantlimitations or inconveniences in accessing network resources, such asthose accessible via displayed links.

BRIEF SUMMARY

The present disclosure is directed towards systems and methods forproviding a preview for a link in a network application. An embeddedbrowser within a client application can provide a mechanism andinterface for users to preview links provided in a network application'ssession (sometimes referred as an HDX session or provisioning session).The network application may be accessed via the client application andthe embedded browser can render a user interface of the networkapplication. A user may click (or otherwise act on) a link (e.g., linkedtext or icon) that is presented within the user interface of the networkapplication. The embedded browser may detect a user action on the link.In some embodiments, when the embedded browser detects the user action,the embedded browser may provide the user an option to open the link inthe embedded browser, for instance in addition to or instead ofinitiating a preview for the link. For instance, when the user acts uponthe link, the user can be provided with an option (e.g., via a selectionmenu) to see a preview or open the link in the embedded browser. If theuser selects the option to see a preview, the embedded browser mayprovide a preview of the link to the user (e.g., in a preview region ofthe embedded browser for the client application).

In one aspect, this disclosure is directed to a method for providing apreview for a link in a network application. The method can includeproviding, by a client application on a client device, access to anetwork application via an embedded browser of the client application.The network application may be hosted on one or more servers, and mayhave a user interface provisioned to the embedded browser via aprovisioning session established with the one or more servers. Themethod can include displaying, in the embedded browser of the clientapplication, a link within the user interface of the networkapplication. The method can include detecting, by a preview engine ofthe client application, a user action on the link displayed in theembedded browser. The method can include providing, by the previewengine of the client application in response to the detected useraction, a preview of the link by rendering the preview in a previewregion of the embedded browser.

In some embodiments, the embedded browser is integrated into the clientapplication. In some embodiments, the method may include causing, by thepreview engine, application of a policy on the link to determine if theembedded browser is allowed to provide the preview. In some embodiments,the method may include providing, by the preview engine, the preview ofthe link responsive to receiving an indication that the embedded browseris allowed to provide the preview.

In some embodiments, the method may include establishing, by the previewengine, the preview region of the embedded browser responsive todetecting the user action on the link. In some embodiments, the previewregion includes a window or a tab of the embedded browser. In someembodiments, the method includes performing, by the preview engine, atleast one of scrolling or resizing the preview within the previewregion.

In some embodiments, the method may include accessing, by the embeddedbrowser responsive to a user action to open the link via the networkapplication, a page of the link for rendering within the user interfaceof the network application. In some embodiments, the method may includesaving, by the embedded browser to a file-sharing application accessedvia the embedded browser, the link responsive to a user action to savethe link. In some embodiments, the method may include detecting, by thepreview engine of the client application, a user action to terminate thepreview. The method may further include closing, by the preview engine,the preview region of the embedded browser.

In another aspect, this disclosure is directed to a system for providinga preview for a link in a network application. The system can include aclient application executable on one or more processors of a clientdevice. The client application can provide access to a networkapplication via an embedded browser of the client application. Thesystem can include the embedded browser of the client applicationexecutable on the one or more processors. The embedded browser candisplay a link within a user interface of the network application. Thesystem can include a preview engine of the client application. Thepreview engine can detect a user action on the link displayed in theembedded browser. The preview engine can provide, in response to thedetected user action, a preview of the link by rendering the preview ina preview region of the embedded browser.

In some embodiments, the embedded browser is integrated into the clientapplication. In some embodiments, the preview engine can causeapplication of a policy on the link to determine if the embedded browseris allowed to provide the preview. In some embodiments, the previewengine can provide the preview of the link responsive to receiving anindication that the embedded browser is allowed to provide the preview.

In some embodiments, the preview engine can establish the preview regionof the embedded browser responsive to detecting the user action on thelink. In some embodiments, the preview region includes a window or a tabof the embedded browser. In some embodiments, the preview engine canperform at least one of scrolling or resizing the preview within thepreview region.

In some embodiments, the embedded browser can access, responsive to auser action to open the link via the network application, a page of thelink for rendering within the user interface of the network application.In some embodiments, the embedded browser can save to a file-sharingapplication accessed via the embedded browser, the link responsive to auser action to save the link. In some embodiments, the preview enginecan detect a user action to terminate the preview. The preview enginecan close the preview region of the embedded browser.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, aspects, features, and advantages ofthe present solution will become more apparent and better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram of embodiments of a computing device;

FIG. 2 is a block diagram of an illustrative embodiment of cloudservices for use in accessing resources;

FIG. 3 is a block diagram of an example embodiment of an enterprisemobility management system;

FIG. 4 is a block diagram of a system 400 of an embedded browser;

FIG. 5 is a block diagram of an example embodiment of a system for usinga secure browser;

FIG. 6 is an example representation of an implementation for browserredirection using a secure browser plug-in;

FIG. 7 is a block diagram of example embodiment of a system of using asecure browser;

FIG. 8 is a block diagram of an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s);

FIG. 9 is an example process flow for using local embedded browser(s)and hosted secured browser(s);

FIG. 10 is an example embodiment of a system for managing user access towebpages;

FIG. 11 is a block diagram of one embodiment of a system for providing apreview of a link in an embedded browser; and

FIG. 12 is a flow diagram of one embodiment of a method for providing apreview of a link in a network application.

The features and advantages of the present solution will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements.

DETAILED DESCRIPTION

For purposes of reading the description of the various embodimentsbelow, the following descriptions of the sections of the specificationand their respective contents may be helpful:

Section A describes a computing environment which may be useful forpracticing embodiments described herein.

Section B describes systems and methods for an embedded browser.

Section C describes systems and methods for providing a preview for alink in a network application.

A. Computing Environment

Prior to discussing the specifics of embodiments of the systems andmethods detailed herein in Section B, it may be helpful to discuss thecomputing environments in which such embodiments may be deployed.

As shown in FIG. 1, computer 101 may include one or more processors 103,volatile memory 122 (e.g., random access memory (RAM)), non-volatilememory 128 (e.g., one or more hard disk drives (HDDs) or other magneticor optical storage media, one or more solid state drives (SSDs) such asa flash drive or other solid state storage media, one or more hybridmagnetic and solid state drives, and/or one or more virtual storagevolumes, such as a cloud storage, or a combination of such physicalstorage volumes and virtual storage volumes or arrays thereof), userinterface (UI) 123, one or more communications interfaces 118, andcommunication bus 150. User interface 123 may include graphical userinterface (GUI) 124 (e.g., a touchscreen, a display, etc.) and one ormore input/output (I/O) devices 126 (e.g., a mouse, a keyboard, amicrophone, one or more speakers, one or more cameras, one or morebiometric scanners, one or more environmental sensors, one or moreaccelerometers, etc.). Non-volatile memory 128 stores operating system115, one or more applications 116, and data 117 such that, for example,computer instructions of operating system 115 and/or applications 116are executed by processor(s) 103 out of volatile memory 122. In someembodiments, volatile memory 122 may include one or more types of RAMand/or a cache memory that may offer a faster response time than a mainmemory. Data may be entered using an input device of GUI 124 or receivedfrom I/O device(s) 126. Various elements of computer 101 may communicatevia one or more communication buses, shown as communication bus 150.

Computer 101 as shown in FIG. 1 is shown merely as an example, asclients, servers, intermediary and other networking devices and may beimplemented by any computing or processing environment and with any typeof machine or set of machines that may have suitable hardware and/orsoftware capable of operating as described herein. Processor(s) 103 maybe implemented by one or more programmable processors to execute one ormore executable instructions, such as a computer program, to perform thefunctions of the system. As used herein, the term “processor” describescircuitry that performs a function, an operation, or a sequence ofoperations. The function, operation, or sequence of operations may behard coded into the circuitry or soft coded by way of instructions heldin a memory device and executed by the circuitry. A “processor” mayperform the function, operation, or sequence of operations using digitalvalues and/or using analog signals. In some embodiments, the “processor”can be embodied in one or more application specific integrated circuits(ASICs), microprocessors, digital signal processors (DSPs), graphicsprocessing units (GPUs), microcontrollers, field programmable gatearrays (FPGAs), programmable logic arrays (PLAs), multi-core processors,or general-purpose computers with associated memory. The “processor” maybe analog, digital or mixed-signal. In some embodiments, the “processor”may be one or more physical processors or one or more “virtual” (e.g.,remotely located or “cloud”) processors. A processor including multipleprocessor cores and/or multiple processors multiple processors mayprovide functionality for parallel, simultaneous execution ofinstructions or for parallel, simultaneous execution of one instructionon more than one piece of data.

Communications interfaces 118 may include one or more interfaces toenable computer 101 to access a computer network such as a Local AreaNetwork (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN),or the Internet through a variety of wired and/or wireless or cellularconnections.

In described embodiments, the computing device 101 may execute anapplication on behalf of a user of a client computing device. Forexample, the computing device 101 may execute a virtual machine, whichprovides an execution session within which applications execute onbehalf of a user or a client computing device, such as a hosted desktopsession. The computing device 101 may also execute a terminal servicessession to provide a hosted desktop environment. The computing device101 may provide access to a computing environment including one or moreof: one or more applications, one or more desktop applications, and oneor more desktop sessions in which one or more applications may execute.

Additional details of the implementation and operation of networkenvironment, computer 101 and client and server computers may be asdescribed in U.S. Pat. No. 9,538,345, issued Jan. 3, 2017 to CitrixSystems, Inc. of Fort Lauderdale, Fla., the teachings of which arehereby incorporated herein by reference.

B. Systems and Methods for an Embedded Browser

The present disclosure is directed towards systems and methods of anembedded browser. A client application executing on a client device canallow a user to access applications (apps) that are served from and/orhosted on one or more servers, such as web applications andsoftware-as-a-service (SaaS) applications (hereafter sometimes generallyreferred to as network applications). A browser that is embedded orintegrated with the client application can render to the user a networkapplication that is accessed or requested via the client application,and can enable interactivity between the user and the networkapplication. The browser is sometimes referred to as an embeddedbrowser, and the client application with embedded browser (CEB) issometimes referred to as a workspace application. The client applicationcan establish a secure connection to the one or more servers to providean application session for the user to access the network applicationusing the client device and the embedded browser. The embedded browsercan be integrated with the client application to ensure that trafficrelated to the network application is routed through and/or processed inthe client application, which can provide the client application withreal-time visibility to the traffic (e.g., when decrypted through theclient application), and user interactions and behavior. The embeddedbrowser can provide a seamless experience to a user as the networkapplication is requested via the user interface (shared by the clientapplication and the embedded browser) and rendered through the embeddedbrowser within the same user interface.

The client application can terminate one end of a secured connectionestablished with a server of a network application, such as a securesockets layer (SSL) virtual private network (VPN) connection. The clientapplication can receive encrypted traffic from the network application,and can decrypt the traffic before further processing (e.g., renderingby the embedded browser). The client application can monitor thereceived traffic (e.g., in encrypted packet form), and also have fullvisibility into the decrypted data stream and/or the SSL stack. Thisvisibility can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control (e.g., to improve performance,service level), and collection and production of analytics. Forinstance, the local CEB can provide an information technology (IT)administrator with a controlled system for deploying web and SaaSapplications through the CEB, and allow the IT administrator to setpolicies or configurations via the CEB for performing any of theforgoing activities.

Many web and SaaS delivered applications connect from web servers togeneric browsers (e.g., Internet Explorer, Firefox, and so on) of users.Once authenticated, the entire session of such a network application isencrypted. However, in this scenario, an administrator may not havevisibility, analytics, or control of the content entering the networkapplication from the user's digital workspace, or the content leavingthe network application and entering the user's digital workspace.Moreover, content of a network application viewed in a generic browsercan be copied or downloaded (e.g., by a user or program) to potentiallyany arbitrary application or device, resulting in a possible breach indata security.

This present systems and methods can ensure that traffic associated witha network application is channeled through a CEB. By way ofillustration, when a user accesses a SaaS web service with securityassertion markup language (SAML) enabled for instance, the correspondingaccess request can be forwarded to a designated gateway service thatdetermines, checks or verifies if the CEB was used to make the accessrequest. Responsive to determining that a CEB was used to make theaccess request, the gateway service can perform or provideauthentication and single-sign-on (SSO), and can allow the CEB toconnect directly to the SaaS web service. Encryption (e.g., standardencryption) can be used for the application session between the CEB andthe SaaS web service. When the content from the web service isunencrypted in the CEB to the viewed via the embedded browser, and/orwhen input is entered via the CEB, the CEB can provide added services onselective application-related information for control and analytics forinstance. For example, an analytics agent or application programminginterface (API) can be embedded in the CEB to provide or perform theadded services.

The CEB (sometimes referred to as workspace application or receiver) caninteroperate with one or more gateway services, intermediaries and/ornetwork servers (sometimes collectively referred to as cloud services orCitrix Cloud) to provide access to a network application. Features andelements of an environment related to the operation of an embodiment ofcloud services are described below.

FIG. 2 illustrates an embodiment of cloud services for use in accessingresources including network applications. The cloud services can includean enterprise mobility technical architecture 200, which can include anaccess gateway 260 in one illustrative embodiment. The architecture canbe used in a bring-your-own-device (BYOD) environment for instance. Thearchitecture can enable a user of a client device 202 (e.g., a mobile orother device) to both access enterprise or personal resources from aclient device 202, and use the client device 202 for personal use. Theuser may access such enterprise resources 204 or enterprise services 208via a client application executing on the client device 202. The usermay access such enterprise resources 204 or enterprise services 208using a client device 202 that is purchased by the user or a clientdevice 202 that is provided by the enterprise to user. The user mayutilize the client device 202 for business use only or for business andpersonal use. The client device may run an iOS operating system, andAndroid operating system, or the like. The enterprise may choose toimplement policies to manage the client device 202. The policies may beimplanted through a firewall or gateway in such a way that the clientdevice may be identified, secured or security verified, and providedselective or full access to the enterprise resources. The policies maybe client device management policies, mobile application managementpolicies, mobile data management policies, or some combination of clientdevice, application, and data management policies. A client device 202that is managed through the application of client device managementpolicies may be referred to as an enrolled device. The client devicemanagement policies can be applied via the client application forinstance.

In some embodiments, the operating system of the client device may beseparated into a managed partition 210 and an unmanaged partition 212.The managed partition 210 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the client device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is not accessibleby unmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The client applicationcan include a secure application launcher 218. The secure applicationsmay be secure native applications 214, secure remote applications 222executed by the secure application launcher 218, virtualizationapplications 226 executed by the secure application launcher 218, andthe like. The secure native applications 214 may be wrapped by a secureapplication wrapper 220. The secure application wrapper 220 may includeintegrated policies that are executed on the client device 202 when thesecure native application is executed on the device. The secureapplication wrapper 220 may include meta-data that points the securenative application 214 running on the client device 202 to the resourceshosted at the enterprise that the secure native application 214 mayrequire to complete the task requested upon execution of the securenative application 214. The secure remote applications 222 executed by asecure application launcher 218 may be executed within the secureapplication launcher application 218. The virtualization applications226 executed by a secure application launcher 218 may utilize resourceson the client device 202, at the enterprise resources 204, and the like.The resources used on the client device 202 by the virtualizationapplications 226 executed by a secure application launcher 218 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 204, and the like. The resources used at theenterprise resources 204 by the virtualization applications 226 executedby a secure application launcher 218 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a graphical user interface (GUI) and communicate them toa server application where the server application may use the userinteraction data as an input to the application operating on the server.In this arrangement, an enterprise may elect to maintain the applicationon the server side as well as data, files, etc., associated with theapplication. While an enterprise may elect to “mobilize” someapplications in accordance with the principles herein by securing themfor deployment on the client device (e.g., via the client application),this arrangement may also be elected for certain applications. Forexample, while some applications may be secured for use on the clientdevice, others might not be prepared or appropriate for deployment onthe client device so the enterprise may elect to provide the mobile useraccess to the unprepared applications through virtualization techniques.As another example, the enterprise may have large complex applicationswith large and complex data sets (e.g., material resource planningapplications) where it would be very difficult, or otherwiseundesirable, to customize the application for the client device so theenterprise may elect to provide access to the application throughvirtualization techniques. As yet another example, the enterprise mayhave an application that maintains highly secured data (e.g., humanresources data, customer data, engineering data) that may be deemed bythe enterprise as too sensitive for even the secured mobile environmentso the enterprise may elect to use virtualization techniques to permitmobile access to such applications and data. An enterprise may elect toprovide both fully secured and fully functional applications on theclient device. The enterprise can use a client application, which caninclude a virtualization application, to allow access to applicationsthat are deemed more properly operated on the server side. In anembodiment, the virtualization application may store some data, files,etc., on the mobile phone in one of the secure storage locations. Anenterprise, for example, may elect to allow certain information to bestored on the phone while not permitting other information.

In connection with the virtualization application, as described herein,the client device may have a virtualization application that is designedto present GUIs and then record user interactions with the GUI. Thevirtualization application may communicate the user interactions to theserver side to be used by the server side application as userinteractions with the application. In response, the application on theserver side may transmit back to the client device a new GUI. Forexample, the new GUI may be a static page, a dynamic page, an animation,or the like, thereby providing access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 228 in the managed partition 210 of the client device. Thedata secured in the secure data container may be accessed by the securewrapped applications 214, applications executed by a secure applicationlauncher 222, virtualization applications 226 executed by a secureapplication launcher 218, and the like. The data stored in the securedata container 228 may include files, databases, and the like. The datastored in the secure data container 228 may include data restricted to aspecific secure application 230, shared among secure applications 232,and the like. Data restricted to a secure application may include securegeneral data 234 and highly secure data 238. Secure general data may usea strong form of encryption such as Advanced Encryption Standard (AES)128-bit encryption or the like, while highly secure data 238 may use avery strong form of encryption such as AES 256-bit encryption. Datastored in the secure data container 228 may be deleted from the deviceupon receipt of a command from the device manager 224. The secureapplications may have a dual-mode option 240. The dual mode option 240may present the user with an option to operate the secured applicationin an unsecured or unmanaged mode. In an unsecured or unmanaged mode,the secure applications may access data stored in an unsecured datacontainer 242 on the unmanaged partition 212 of the client device 202.The data stored in an unsecured data container may be personal data 244.The data stored in an unsecured data container 242 may also be accessedby unsecured applications 248 that are running on the unmanagedpartition 212 of the client device 202. The data stored in an unsecureddata container 242 may remain on the client device 202 when the datastored in the secure data container 228 is deleted from the clientdevice 202. An enterprise may want to delete from the client deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The client device 202 may connect to enterprise resources 204 andenterprise services 208 at an enterprise, to the public Internet 248,and the like. The client device may connect to enterprise resources 204and enterprise services 208 through virtual private network connections.The virtual private network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications(e.g., as illustrated by microVPNs 250), particular devices, particularsecured areas on the client device (e.g., as illustrated by O/S VPN252), and the like. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 254. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 258. The authentication service 258 may thengrant to the user access to multiple enterprise resources 204, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 204.

The virtual private network connections may be established and managedby an access gateway 260. The access gateway 260 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 204 to the client device 202. The access gatewaymay also re-route traffic from the client device 202 to the publicInternet 248, enabling the client device 202 to access publiclyavailable and unsecured applications that run on the public Internet248. The client device may connect to the access gateway via a transportnetwork 262. The transport network 262 may use one or more transportprotocols and may be a wired network, wireless network, cloud network,local area network, metropolitan area network, wide area network, publicnetwork, private network, and the like.

The enterprise resources 204 may include email servers, file sharingservers, SaaS/Web applications, Web application servers, Windowsapplication servers, and the like. Email servers may include Exchangeservers, Lotus Notes servers, and the like. File sharing servers mayinclude ShareFile servers, and the like. SaaS applications may includeSalesforce, and the like. Windows application servers may include anyapplication server that is built to provide applications that areintended to run on a local Windows operating system, and the like. Theenterprise resources 204 may be premise-based resources, cloud basedresources, and the like. The enterprise resources 204 may be accessed bythe client device 202 directly or through the access gateway 260. Theenterprise resources 204 may be accessed by the client device 202 via atransport network 262. The transport network 262 may be a wired network,wireless network, cloud network, local area network, metropolitan areanetwork, wide area network, public network, private network, and thelike.

Cloud services can include an access gateway 260 and/or enterpriseservices 208. The enterprise services 208 may include authenticationservices 258, threat detection services 264, device manager services224, file sharing services 268, policy manager services 270, socialintegration services 272, application controller services 274, and thelike. Authentication services 258 may include user authenticationservices, device authentication services, application authenticationservices, data authentication services and the like. Authenticationservices 258 may use certificates. The certificates may be stored on theclient device 202, by the enterprise resources 204, and the like. Thecertificates stored on the client device 202 may be stored in anencrypted location on the client device, the certificate may betemporarily stored on the client device 202 for use at the time ofauthentication, and the like. Threat detection services 264 may includeintrusion detection services, unauthorized access attempt detectionservices, and the like. Unauthorized access attempt detection servicesmay include unauthorized attempts to access devices, applications, data,and the like. Device management services 224 may include configuration,provisioning, security, support, monitoring, reporting, anddecommissioning services. File sharing services 268 may include filemanagement services, file storage services, file collaboration services,and the like. Policy manager services 270 may include device policymanager services, application policy manager services, data policymanager services, and the like. Social integration services 272 mayinclude contact integration services, collaboration services,integration with social networks such as Facebook, Twitter, andLinkedIn, and the like. Application controller services 274 may includemanagement services, provisioning services, deployment services,assignment services, revocation services, wrapping services, and thelike.

The enterprise mobility technical architecture 200 may include anapplication store 278. The application store 278 may include unwrappedapplications 280, pre-wrapped applications 282, and the like.Applications may be populated in the application store 278 from theapplication controller 274. The application store 278 may be accessed bythe client device 202 through the access gateway 260, through the publicInternet 248, or the like. The application store may be provided with anintuitive and easy to use User Interface.

A software development kit 284 may provide a user the capability tosecure applications selected by the user by providing a secure wrapperaround the application. An application that has been wrapped using thesoftware development kit 284 may then be made available to the clientdevice 202 by populating it in the application store 278 using theapplication controller 274.

The enterprise mobility technical architecture 200 may include amanagement and analytics capability. The management and analyticscapability may provide information related to how resources are used,how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 3 depicts is an illustrative embodiment of an enterprise mobilitymanagement system 300. Some of the components of the mobility managementsystem 200 described above with reference to FIG. 2 have been omittedfor the sake of simplicity. The architecture of the system 300 depictedin FIG. 3 is similar in many respects to the architecture of the system200 described above with reference to FIG. 2 and may include additionalfeatures not mentioned above.

In this case, the left hand side represents an enrolled client device302 with a client agent 304, which interacts with gateway server 306 toaccess various enterprise resources 308 and services 309 such as Web orSasS applications, Exchange, Sharepoint, public-key infrastructure (PKI)Resources, Kerberos Resources, Certificate Issuance service, as shown onthe right hand side above. The gateway server 306 can includeembodiments of features and functionalities of the cloud services, suchas access gateway 260 and application controller functionality. Althoughnot specifically shown, the client agent 304 may be part of, and/orinteract with the client application which can operate as an enterpriseapplication store (storefront) for the selection and/or downloading ofnetwork applications.

The client agent 304 can act as a UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX) or IndependentComputing Architecture (ICA) display remoting protocol. The client agent304 can also support the installation and management of nativeapplications on the client device 302, such as native iOS or Androidapplications. For example, the managed applications 310 (mail, browser,wrapped application) shown in the figure above are native applicationsthat execute locally on the device. Client agent 304 and applicationmanagement framework of this architecture act to provide policy drivenmanagement capabilities and features such as connectivity and SSO(single sign on) to enterprise resources/services 308. The client agent304 handles primary user authentication to the enterprise, for instanceto access gateway (AG) with SSO to other gateway server components. Theclient agent 304 obtains policies from gateway server 306 to control thebehavior of the managed applications 310 on the client device 302.

The Secure interprocess communication (IPC) links 312 between the nativeapplications 310 and client agent 304 represent a management channel,which allows client agent to supply policies to be enforced by theapplication management framework 314 “wrapping” each application. TheIPC channel 312 also allows client agent 304 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 308. Finally the IPC channel 312 allows theapplication management framework 314 to invoke user interface functionsimplemented by client agent 304, such as online and offlineauthentication.

Communications between the client agent 304 and gateway server 306 areessentially an extension of the management channel from the applicationmanagement framework 314 wrapping each native managed application 310.The application management framework 314 requests policy informationfrom client agent 304, which in turn requests it from gateway server306. The application management framework 314 requests authentication,and client agent 304 logs into the gateway services part of gatewayserver 306 (also known as NetScaler access gateway). Client agent 304may also call supporting services on gateway server 306, which mayproduce input material to derive encryption keys for the local datavaults 316, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 314 “wraps” eachmanaged application 310. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 314 may “pair” with client agent 304 on first launch of anapplication 310 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 314may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 310.

The application management framework 314 may use services provided byclient agent 304 over the Secure IPC channel 312 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 316 (containers) may be also managed byappropriate interactions between the managed applications 310 and clientagent 304. Vaults 316 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 316 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 310 through access gateway 306. The applicationmanagement framework 314 is responsible for orchestrating the networkaccess on behalf of each application 310. Client agent 304 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 318.

The Mail and Browser managed applications 310 can have special statusand may make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture can support the incorporation of various othersecurity features. For example, gateway server 306 (including itsgateway services) in some cases might not need to validate activedirectory (AD) passwords. It can be left to the discretion of anenterprise whether an AD password is used as an authentication factorfor some users in some situations. Different authentication methods maybe used if a user is online or offline (i.e., connected or not connectedto a network).

Step up authentication is a feature wherein gateway server 306 mayidentify managed native applications 310 that are allowed to have accessto more sensitive data using strong authentication, and ensure thataccess to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequested from the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 316 (containers) on the client device 302. The vaults 316 may beencrypted so that all on-device data including clipboard/cache data,files, databases, and configurations are protected. For on-line vaults,the keys may be stored on the server (gateway server 306), and foroff-line vaults, a local copy of the keys may be protected by a userpassword or biometric validation. When data is stored locally on thedevice 302 in the secure container 316, it is preferred that a minimumof AES 256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 310 are logged and reported to the backend. Datawiping may be supported, such as if the application 310 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase or biometric data supplied by the user (ifoffline access is required). It may be XORed with another key randomlygenerated and stored on the server side if offline access is notrequired. Key Derivation functions may operate such that keys generatedfrom the user password use KDFs (key derivation functions, notablyPassword-Based Key Derivation Function 2 (PBKDF2)) rather than creatinga cryptographic hash of it. The latter makes a key susceptible to bruteforce or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector might cause multiple copies of thesame encrypted data to yield different cipher text output, preventingboth replay and cryptanalytic attacks. This may also prevent an attackerfrom decrypting any data even with a stolen encryption key. Further,authentication then decryption may be used, wherein application data isdecrypted only after the user has authenticated within the application.Another feature may relate to sensitive data in memory, which may bekept in memory (and not in disk) only when it's needed. For example,login credentials may be wiped from memory after login, and encryptionkeys and other data inside objective-C instance variables are notstored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented via the CEB, wherein after apolicy-defined period of inactivity, a user session is terminated.

Data leakage from the application management framework 314 may beprevented in other ways. For example, when an application 310 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 320 without the use of an AD (active directory) 322 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 320 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 320. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 310 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want storefront to be accessed inthis manner. In this case, the client agent 304 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 306 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 310 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application may utilizesuch a certificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from theclient agent 304 may be retrieved by gateway server 306 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in gateway server306.

Gateway server 306 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 304 and the application management framework 314 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting public-key cryptography standards (PKCS) 12 BLOB (Binary LargeObject) into the iOS keychain in each managed application for eachperiod of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate might never be present in the iOSkeychain and might not be persisted except potentially in “online-only”data value that is strongly protected.

Mutual SSL or TLS may also be implemented to provide additional securityby requiring that a client device 302 is authenticated to theenterprise, and vice versa. Virtual smart cards for authentication togateway server 306 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 322, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when http (but not https) connections areproxied in VPN and MicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may includeremote wipe functionality even when an application 310 is not running.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be service from one of several different locations in case offailure.

In some cases, managed applications 310 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 310 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is used, when an application reads a certificate for“who am I,” when an application uses the certificate to build a securesession token, and when an application uses private keys for digitalsigning of important data (e.g., transaction log) or for temporary dataencryption.

Referring now to FIG. 4, depicted is a block diagram of a system 400 ofan embedded browser. In brief overview, the system 400 may include aclient device 402 with a digital workspace for a user, a clientapplication 404, cloud services 408 operating on at least one networkdevice 432, and network applications 406 served from and/or hosted onone or more servers 430. The client application 404 can for instanceinclude at least one of: an embedded browser 410, a networking agent412, a cloud services agent 414, a remote session agent 416, or a securecontainer 418. The cloud services 408 can for instance include at leastone of: secure browser(s) 420, an access gateway 422 (or CIS, e.g., forregistering and/or authenticating the client application and/or user),or analytics services 424 (or CAS, e.g., for receiving information fromthe client application for analytics). The network applications 406 caninclude sanctioned applications 426 and non-sanctioned applications 428.

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 400 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the client device 402, the at least one network device 432and/or the one or more servers 430. The hardware includes circuitry suchas one or more processors in one or more embodiments. For example, theat least one network device 432 and/or the one or more servers 430 caninclude any of the elements of a computing device described above inconnection with at least FIG. 1 for instance.

The client device 402 can include any embodiment of a computing devicedescribed above in connection with at least FIG. 1 for instance. Theclient device 402 can include any user device such as a desktopcomputer, a laptop computer, a tablet device, a smart phone, or anyother mobile or personal device. The client device 402 can include adigital workspace of a user, which can include file system(s), cache ormemory (e.g., including electronic clipboard(s)), container(s),application(s) and/or other resources on the client device 402. Thedigital workspace can include or extend to one or more networksaccessible by the client device 402, such as an intranet and theInternet, including file system(s) and/or other resources accessible viathe one or more networks. A portion of the digital workspace can besecured via the use of the client application 404 with embedded browser410 (CEB) for instance. The secure portion of the digital workspace caninclude for instance file system(s), cache or memory (e.g., includingelectronic clipboard(s)), application(s), container(s) and/or otherresources allocated to the CEB, and/or allocated by the CEB to networkapplication(s) 406 accessed via the CEB. The secure portion of thedigital workspace can also include resources specified by the CEB (viaone or more policies) for inclusion in the secure portion of the digitalworkspace (e.g., a particular local application can be specified via apolicy to be allowed to receive data obtained from a networkapplication).

The client application 404 can include one or more components, such asan embedded browser 410, a networking agent 412, a cloud services agent414 (sometimes referred to as management agent), a remote session agent416 (sometimes referred to as HDX engine), and/or a secure container 418(sometimes referred to as secure cache container). One or more of thecomponents can be installed as part of a software build or release ofthe client application 404 or CEB, or separately acquired or downloadedand installed/integrated into an existing installation of the clientapplication 404 or CEB for instance. For instance, the client device maydownload or otherwise receive the client application 404 (or anycomponent) from the network device(s) 432. In some embodiments, theclient device may send a request for the client application 404 to thenetwork device(s) 432. For example, a user of the client device caninitiate a request, download and/or installation of the clientapplication. The network device(s) 432 in turn may send the clientapplication to the client device. In some embodiments, the networkdevice(s) 432 may send a setup or installation application for theclient application to the client device. Upon receipt, the client devicemay install the client application onto a hard disk of the clientdevice. In some embodiments, the client device may run the setupapplication to unpack or decompress a package of the client application.In some embodiments, the client application may be an extension (e.g.,an add-on, an add-in, an applet or a plug-in) to another application(e.g., a networking agent 412) installed on the client device. Theclient device may install the client application to interface orinter-operate with the pre-installed application. In some embodiments,the client application may be a standalone application. The clientdevice may install the client application to execute as a separateprocess.

The embedded browser 410 can include elements and functionalities of aweb browser application or engine. The embedded browser 410 can locallyrender network application(s) as a component or extension of the clientapplication. For instance, the embedded browser 410 can render aSaaS/Web application inside the CEB which can provide the CEB with fullvisibility and control of the application session. The embedded browsercan be embedded or incorporated into the client application via anymeans, such as direct integration (e.g., programming language or scriptinsertion) into the executable code of the client application, or viaplugin installation. For example, the embedded browser can include aChromium based browser engine or other type of browser engine, that canbe embedded into the client application, using the Chromium embeddedframework (CEF) for instance. The embedded browser can include aHTML5-based layout graphical user interface (GUI). The embedded browsercan provide HTML rendering and JavaScript support to a clientapplication incorporating various programming languages. For example,elements of the embedded browser can bind to a client applicationincorporating C, C++, Delphi, Go, Java, .NET/Mono, Visual Basic 6.0,and/or Python.

In some embodiments, the embedded browser comprises a plug-in installedon the client application. For example, the plug-in can include one ormore components. One such component can be an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the client application. For example,the client application can load and run an Active X control of theembedded browser, such as in a memory space or context of the clientapplication. In some embodiments, the embedded browser can be installedas an extension on the client application, and a user can choose toenable or disable the plugin or extension. The embedded browser (e.g.,via the plugin or extension) can form or operate as a secured browserfor securing, using and/or accessing resources within the securedportion of the digital workspace.

The embedded browser can incorporate code and functionalities beyondthat available or possible in a standard or typical browser. Forinstance, the embedded browser can bind with or be assigned with asecured container 418, to define at least part of the secured portion ofa user's digital workspace. The embedded browser can bind with or beassigned with a portion of the client device's cache to form a securedclipboard (e.g., local to the client device, or extendable to otherdevices), that can be at least part of the secured container 418. Theembedded browser can be integrated with the client application to ensurethat traffic related to network applications is routed through and/orprocessed in the client application, which can provide the clientapplication with real-time visibility to the traffic (e.g., whendecrypted through the client application). This visibility to thetraffic can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control, and collection and production ofanalytics.

In some embodiments, the embedded browser incorporates one or more othercomponents of the client application 404, such as the cloud servicesagent 414, remote session agent 416 and/or secure container 418. Forinstance, a user can use the cloud services agent 414 of the embeddedbrowser to interoperate with the access gateway 422 (sometimes referredto as CIS) to access a network application. For example, the cloudservices agent 414 can execute within the embedded browser, and canreceive and transmit navigation commands from the embedded browser to ahosted network application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

The client application 404 and CEB operate on the application layer ofthe operational (OSI) stack of the client device. The client application404 can include and/or execute one or more agents that interoperate withthe cloud services 408. The client application 404 can receive, obtain,retrieve or otherwise access various policies (e.g., an enterprise'scustom, specified or internal policies or rules) and/or data (e.g., froman access gateway 422 and/or network device(s) of cloud services 408, orother server(s), that may be managed by the enterprise). The clientapplication can access the policies and/or data to control and/or managea network application (e.g., a SaaS, web or remote-hosted application).Control and/or management of a network application can include controland/or management of various aspects of the network application, such asaccess control, session delivery, available features or functions,service level, traffic management and monitoring, and so on. The networkapplication can be from a provider or vendor of the enterprise (e.g.,salesforce.com, SAP, Microsoft Office 365), from the enterprise itself,or from another entity (e.g., Dropbox or Gmail service).

For example, the cloud services agent 414 can provide policy drivenmanagement capabilities and features related to the use and/or access ofnetwork applications. For example, the cloud services agent 414 caninclude a policy engine to apply one or more policies (e.g., receivedfrom cloud services) to determine access control and/or connectivity toresources such as network applications. When a session is establishedbetween the client application and a server 430 providing a SaaSapplication for instance, the cloud services agent 414 can apply one ormore policies to control traffic levels and/or traffic types (or otheraspects) of the session, for instance to manage a service level of theSaaS application. Additional aspects of the application traffic that canbe controlled or managed can include encryption level and/or encryptiontype applied to the traffic, level of interactivity allowed for a user,limited access to certain features of the network application (e.g.,print-screen, save, edit or copy functions), restrictions to use ortransfer of data obtained from the network application, limit concurrentaccess to two or more network applications, limit access to certain filerepositories or other resources, and so on.

The cloud services agent 414 can convey or feed information to analyticsservices 424 of the cloud services 408, such as information about SaaSinteraction events visible to the CEB. Such a configuration using theCEB can monitor or capture information for analytics without having aninline device or proxy located between the client device and theserver(s) 430, or using a SaaS API gateway ‘out-of-band’ approach. Insome embodiments, the cloud services agent 414 does not execute withinthe embedded browser. In these embodiments, a user can similarly use thecloud services agent 414 to interoperate with the access gateway (orCIS) 422 to access a network application. For instance, the cloudservices agent 414 can register and/or authenticate with the accessgateway (or CIS) 422, and can obtain a list of the network applicationsfrom the access gateway (or CIS) 422. The cloud services agent 414 caninclude and/or operate as an application store (or storefront) for userselection and/or downloading of network applications. Upon logging in toaccess a network application, the cloud services agent 414 can interceptand transmit navigation commands from the embedded browser to thenetwork application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

In some embodiments, the cloud services agent 414 provides single signon (SSO) capability for the user and/or client device to access aplurality of network applications. The cloud services agent 414 canperform user authentication to access network applications as well asother network resources and services, by communicating with the accessgateway 422 for instance. For example, the cloud services agent 414 canauthenticate or register with the access gateway 422, to access othercomponents of the cloud services 408 and/or the network applications406. Responsive to the authentication or registration, the accessgateway 422 can perform authentication and/or SSO for (or on behalf of)the user and/or client application, with the network applications.

The client application 404 can include a networking agent 412. Thenetworking agent 412 is sometimes referred to as a software-defined widearea network (SD-WAN) agent, mVPN agent, or microVPN agent. Thenetworking agent 412 can establish or facilitate establishment of anetwork connection between the client application and one or moreresources (e.g., server 430 serving a network application). Thenetworking agent 412 can perform handshaking for a requested connectionfrom the client application to access a network application, and canestablish the requested connection (e.g., secure or encryptedconnection). The networking agent 412 can connect to enterpriseresources (including services) for instance via a virtual privatenetwork (VPN). For example, the networking agent 412 can establish asecure socket layer (SSL) VPN between the client application and aserver 430 providing the network application 406. The VPN connections,sometimes referred to as microVPN or application-specific VPN, may bespecific to particular network applications, particular devices,particular secured areas on the client device, and the like, forinstance as discussed above in connection with FIG. 3. Such VPNconnections can carry Microsoft Exchange traffic, Microsoft ActiveDirectory traffic, HyperText Transfer Protocol (HTTP) traffic, HyperTextTransfer Protocol Secure (HTTPS) traffic, as some examples.

The remote session agent 416 (sometimes referred to as HDX engine) caninclude features of the client agent 304 discussed above in connectionwith FIG. 2 for instance, to support display a remoting protocol (e.g.,HDX or ICA). In some embodiments, the remote session agent 416 canestablish a remote desktop session and/or remote application session inaccordance to any variety of protocols, such as the Remote DesktopProtocol (RDP), Appliance Link Protocol (ALP), Remote Frame Buffer (RFB)Protocol, and ICA Protocol. For example, the remote session agent 416can establish a remote application session for a user of the clientdevice to access an enterprise network application. The remote sessionagent 416 can establish the remote application session within or over asecure connection (e.g., a VPN) established by the networking agent 412for instance.

The client application or CEB can include or be associated with a securecontainer 418. A secure container can include a logical or virtualdelineation of one or more types of resources accessible within theclient device and/or accessible by the client device. For example, thesecure container 418 can refer to the entirety of the secured portion ofthe digital workspace, or particular aspect(s) of the secured portion.In some embodiments, the secure container 418 corresponds to a securecache (e.g., electronic or virtual clipboard), and can dynamicallyincorporate a portion of a local cache of each client device of a user,and/or a cloud-based cache of the user, that is protected or secured(e.g., encrypted). The secure container can define a portion of filesystem(s), and/or delineate resources allocated to a CEB and/or tonetwork applications accessed via the CEB. The secure container caninclude elements of the secure data container 228 discussed above inconnection with FIG. 2 for example. The CEB can be configured (e.g., viapolicies) to limit, disallow or disable certain actions or activities onresources and/or data identified to be within a secure container. Asecured container can be defined to specify that the resources and/ordata within the secure container are to be monitored for misuse, abuseand/or exfiltration.

In certain embodiments, a secure container relates to or involves theuse of a secure browser (e.g., embedded browser 410 or secure browser420) that implements various enterprise security features. Networkapplications (or web pages accessed by the secure browser) that areconfigured to run within the secure browser can effectively inherit thesecurity mechanisms implemented by the secure browser. These networkapplications can be considered to be contained within the securecontainer. The use of such a secure browser can enable an enterprise toimplement a content filtering policy in which, for example, employeesare blocked from accessing certain web sites from their client devices.The secure browser can be used, for example, to enable client deviceusers to access a corporate intranet without the need for a VPN.

In some embodiments, a secure container can support various types ofremedial actions for protecting enterprise resources. One such remedy isto lock the client device, or a secure container on the client devicethat stores data to be protected, such that the client device or securecontainer can only be unlocked with a valid code provided by anadministrator for instance. In some embodiments, these and other typesof remedies can be invoked automatically based on conditions detected onthe client device (via the application of policies for instance), or canbe remotely initiated by an administrator.

In some embodiments, a secure container can include a secure documentcontainer for documents. A document can comprise any computer-readablefile including text, audio, video, and/or other types of information ormedia. A document can comprise any single one or combination of thesemedia types. As explained herein, the secure container can help preventthe spread of enterprise information to different applications andcomponents of the client device, as well as to other devices. Theenterprise system (which can be partially or entirely within a cloudnetwork) can transmit documents to various devices, which can be storedwithin the secure container. The secure container can preventunauthorized applications and other components of the client device fromaccessing information within the secure container. For enterprises thatallow users to use their own client devices for accessing, storing, andusing enterprise data, providing secure container on the client deviceshelps to secure the enterprise data. For instance, providing securecontainers on the client devices can centralize enterprise data in onelocation on each client device, and can facilitate selective or completedeletion of enterprise data from each client device when desired.

The secure container can include an application that implements a filesystem that stores documents and/or other types of files. The filesystem can comprise a portion of a computer-readable memory of theclient device. The file system can be logically separated from otherportions of the computer-readable memory of the client device. In thisway, enterprise data can be stored in a secure container and privatedata can be stored in a separate portion of the computer-readable memoryof the client device for instance. The secure container can allow theCEB, network applications accessed via the CEB, locally installedapplications and/or other components of the client device to read from,write to, and/or delete information from the file system (if authorizedto do so). Deleting data from the secure container can include deletingactual data stored in the secure container, deleting pointers to datastored in the secure container, deleting encryption keys used to decryptdata stored in the secure container, and the like. The secure containercan be installed by, e.g., the client application, an administrator, orthe client device manufacturer. The secure container can enable some orall of the enterprise data stored in the file system to be deletedwithout modifying private data stored on the client device outside ofthe secure container. The file system can facilitate selective orcomplete deletion of data from the file system. For example, anauthorized component of the enterprise's system can delete data from thefile system based on, e.g., encoded rules. In some embodiments, theclient application can delete the data from the file system, in responseto receiving a deletion command from the enterprise's system.

The secure container can include an access manager that governs accessto the file system by applications and other components of the clientdevice. Access to the file system can be governed based on documentaccess policies (e.g., encoded rules) maintained by the clientapplication, in the documents and/or in the file system. A documentaccess policy can limit access to the file system based on (1) whichapplication or other component of the client device is requestingaccess, (2) which documents are being requested, (3) time or date, (4)geographical position of the client device, (5) whether the requestingapplication or other component provides a correct certificate orcredentials, (6) whether the user of the client device provides correctcredentials, (7) other conditions, or any combination thereof. A user'scredentials can comprise, for example, a password, one or more answersto security questions (e.g., What is the mascot of your high school?),biometric information (e.g., fingerprint scan, eye-scan), and the like.Hence, by using the access manager, the secure container can beconfigured to be accessed only by applications that are authorized toaccess the secure container. As one example, the access manager canenable enterprise applications installed on the client device to accessdata stored in the secure container and to prevent non-enterpriseapplications from accessing the data stored in the secure container.

Temporal and geographic restrictions on document access may be useful.For example, an administrator may deploy a document access policy thatrestricts the availability of the documents (stored within the securecontainer) to a specified time window and/or a geographic zone (e.g., asdetermined by a GPS chip) within which the client device must reside inorder to access the documents. Further, the document access policy caninstruct the secure container or client application to delete thedocuments from the secure container or otherwise make them unavailablewhen the specified time period expires or if the client device is takenoutside of the defined geographic zone.

Some documents can have access policies that forbid the document frombeing saved within the secure container. In such embodiments, thedocument can be available for viewing on the client device only when theuser is logged in or authenticated via the cloud services for example.

The access manager can also be configured to enforce certain modes ofconnectivity between remote devices (e.g., an enterprise resource orother enterprise server) and the secure container. For example, theaccess manager can require that documents received by the securecontainer from a remote device and/or sent from the secure container tothe remote device be transmitted through secured tunnels/connections,for example. The access manager can require that all documentstransmitted to and from the secure container be encrypted. The clientapplication or access manager can be configured to encrypt documentssent from the secure container and decrypt documents sent to the securecontainer. Documents in the secure container can also be stored in anencrypted form.

The secure container can be configured to prevent documents or dataincluded within documents or the secure container from being used byunauthorized applications or components of the client device or otherdevices. For instance, a client device application having authorizationto access documents from the secure container can be programmed toprevent a user from copying a document's data and pasting it intoanother file or application interface, or locally saving the document ordocument data as a new file outside of the secure container. Similarly,the secure container can include a document viewer and/or editor that donot permit such copy/paste and local save operations. Moreover, theaccess manager can be configured to prevent such copy/paste and localsave operations. Further, the secure container and applicationsprogrammed and authorized to access documents from the secure containercan be configured to prevent users from attaching such documents toemails or other forms of communication.

One or more applications (e.g., applications installed on the clientdevice, and/or network applications accessed via the CEB) can beprogrammed or controlled (e.g., via policy-based enforcement) to writeenterprise-related data only into the secure container. For instance, anapplication's source code can be provided with the resource name of thesecure container. Similarly, a remote application (e.g., executing on adevice other than the client device) can be configured to send data ordocuments only to the secure container (as opposed to other componentsor memory locations of the client device). Storing data to the securecontainer can occur automatically, for example, under control of theapplication, the client application, and/or the secure browser. Theclient application can be programmed to encrypt or decrypt documentsstored or to be stored within the secure container. In certainembodiments, the secure container can only be used by applications (onthe client device or a remote device) that are programmed to identifyand use the secure container, and which have authorization to do so.

The network applications 406 can include sanctioned network applications426 and non-sanctioned network applications 428. By way of anon-limiting example, sanctioned network applications 426 can includenetwork applications from Workday, Salesforce, Office 365, SAP, and soon, while non-sanctioned network applications 426 can include networkapplications from Dropbox, Gmail, and so on. For instance, FIG. 4illustrates a case where sanctioned applications 426 are accessed via aCEB. In operation (1), a user instance of a client application 404, thatis installed on client device 402, can register or authenticate with theaccess gateway 422 of cloud services 408. For example, the user canauthenticate the user to the client device and login to the clientdevice 402. The client application can automatically execute, or beactivated by the user. In some embodiments, the user can sign in to theclient application (e.g., by authenticating the user to the clientapplication). In response to the login or sign-in, the clientapplication can register or authenticate the user and/or the clientapplication with the access gateway 422.

In operation (2), in response to the registration or authentication, theaccess gateway 422 can identify or retrieve a list of enumerated networkapplications available or pre-assigned to the user, and can provide thelist to the client application. For example, in response to theregistration or authentication, the access gateway can identify the userand/or retrieve a user profile of the user. According to the identityand/or user profile, the access gateway can determine the list (e.g.,retrieve a stored list of network applications matched with the userprofile and/or the identity of the user). The list can correspond to alist of network applications sanctioned for the user. The access gatewaycan send the list to the client application or embedded browser, whichcan be presented via the client application or embedded browser to theuser (e.g., in a storefront user interface) for selection.

In operation (3), the user can initiate connection to a sanctionednetwork application (e.g., a SaaS application), by selecting from thelist of network applications presented to the user. For example, theuser can click on an icon or other representation of the sanctionednetwork application, displayed via the client application or embeddedbrowser. This user action can trigger the CEB to transmit a connectionor access request to a server that provisions the network application.The request can include a request to the server (e.g., SaaS provider) tocommunicate with the access gateway to authenticate the user. The servercan send a request to the access gateway to authenticate the user forexample.

In operation (4), the access gateway can perform SSO with the server, toauthenticate the user. For example, in response to the server's requestto authenticate the user, the access gateway can provide credentials ofthe user to the server(s) 430 for SSO, to access the selected networkapplication and/or other sanctioned network applications. In operation(5), the user can log into the selected network application, based onthe SSO (e.g., using the credentials). The client application (e.g., thenetworking agent 412 and/or the remote session agent 416) can establisha secure connection and session with the server(s) 430 to access theselected network application. The CEB can decrypt application trafficreceived via the secure connection. The CEB can monitor traffic sent viathe CEB and the secured connection to the servers 430.

In operation (6), the client application can provide information to theanalytics services 424 of cloud services 408, for analytics processing.For example, the cloud services agent 414 of the client application 404can monitor for or capture user interaction events with the selectednetwork application. The cloud services agent 414 can convey the userinteraction events to the analytics services 424, to be processed toproduce analytics.

FIG. 5 depicts an example embodiment of a system for using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 4, but that the client application (with embedded browser) is notavailable in the client device 402. A standard or typical browser may beavailable on the client device, from which a user can initiate a requestto access a sanctioned network application for instance. A networkapplication can be specified as being sanctioned or unsanctioned viapolicies that can be set by an administrator or automatically (e.g., viaartificial intelligence).

For example, in operation (1), the user may log into the networkapplication using the standard browser. For accessing a sanctionednetwork application, the user may access a predefined URL and/orcorresponding webpage of a server that provisions the networkapplication, via the standard browser, to initiate a request to accessthe network application. In some embodiments, the request can beforwarded to or intercepted by a designated gateway service (e.g., in adata path of the request). For example, the gateway service can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. In someembodiments, the access gateway can correspond to or include the gatewayservice. The gateway service can determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB. In some embodiments, there is no requirement for adesignated gateway service to detect or determine if the request isinitiated from a CEB, for example if the requested network applicationis sanctioned, that user is initiating the request via a standardbrowser, and/or that the predefined URL and/or corresponding webpage isaccessed.

In operation (2), the server may authenticate the user via the accessgateway of the cloud services 408. The server may communicate with theaccess gateway to authenticate the user, in response to the request. Forinstance, the request can include an indication to the server tocommunicate with the access gateway to authenticate the user. In someembodiments, the server is pre-configured to communicate with the accessgateway to authenticate the user, for requests to access a sanctionednetwork application. The server may send a request to the access gatewayto authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430.

In operation (3), the gateway service and/or the server can direct (orredirect) all traffic to a secure browser 420 which provides a securebrowsing service. This may be in response to at least one of: adetermination that the requested network application is a sanctionednetwork application, a determination that the request is initiated froma source other than a CEB, a determination that the requested networkapplication is sanctioned, a determination that user is initiating therequest via a standard browser, and/or a determination that thepredefined URL and/or corresponding webpage is accessed.

The user's URL session can be redirected to the secure browser. Forexample, the server, gateway service and/or the access gateway cangenerate and/or send a URL redirect message to the standard browser,responsive to the determination. The secure browser plug-in of thestandard browser can receive the URL redirect message, and can forexample send a request to access the non-sanctioned network application,to the secure browser 420. The secure browser 420 can direct the requestto the server of the non-sanctioned network application. The URLredirect message can instruct the standard browser (and/or the securebrowser plug-in) to direct traffic (e.g., destined for the networkapplication) from the standard browser to the secure browser 420 hostedon a network device. This can provide clientless access and control viadynamic routing though a secure browser service. In some embodiments, aredirection of all traffic to the secure browser 420 is initiated orconfigured, prior to performing authentication of the user (e.g., usingSSO) with the server.

In some embodiments, the gateway service can direct or request theserver of the requested network application to communicate with thesecure browser 420. For example, the gateway service can direct theserver and/or the secure browser to establish a secured connectionbetween the server and the secure browser, for establishing anapplication session for the network application.

In some embodiments, the secured browser 420 comprises a browser that ishosted on a network device 432 of the cloud services 408. The securedbrowser 420 can include one or more features of the secured browser 420described above in connection with at least FIG. 4 for instance. Thehosted browser can include an embedded browser of a CEB that is hostedon the network device 432 instead of on the client device. The hostedbrowser can include an embedded browser of a hosted virtualized versionof the CEB that is hosted on the network device 432. Similar to the CEBinstalled on the client device, traffic is routed through the CEB hostedon the network device, which allows an administrator to have visibilityof the traffic through the CEB and to remain in control for securitypolicy control, analytics, and/or management of performance.

FIG. 6 illustrates an example implementation for browser redirectionusing a secure browser plug-in. In brief overview, the implementationincludes a web browser 512 with a secure browser plug-in 516 operatingon a client device, and a hosted web browser (or secure browser) 522residing on a network device. The web browser 512 can correspond to astandard browser, instead of an embedded browser as discussed above inconnection with FIG. 4 for example. The secure browser plug-in 516 canexecute within a first network 510 and access a server 430 in a secondnetwork 530. The first network 510 and the second network 530 are forillustration purposes and may be replaced with fewer or additionalcomputer networks. A secure browser plug-in 516 can be installed on thestandard browser 512. The plug-in can include one or more components.One such component can include an ActiveX control or Java control or anyother type and/or form of executable instructions capable of loadinginto and executing in the standard browser. For example, the standardbrowser can load and run an Active X control of the secure browserplug-in 516, in a memory space or context of the standard browser. Insome embodiments, the secure browser plug-in can be installed as anextension on the standard browser, and a user can choose to enable ordisable the plugin or extension. The secure browser plug-in cancommunicate and/or operate with the secured browser 420 for securing,using and/or accessing resources within the secured portion of thedigital workspace.

By using the secure browser plug-in 516 operating within the standardbrowser 512 network applications accessed via the standard browser 512can be redirected to a hosted secure browser. For instance, the securebrowser plug-in 516 can be implemented and/or designed to detect that anetwork application is being accessed via the standard browser, and candirect/redirect traffic from the client device associated with thenetwork application, to the hosted secure browser. The hosted securebrowser can direct traffic received from the network application, to thesecure browser plug-in 516 and/or a client agent 514 for renderingand/or display for example. The client agent 514 can execute within theweb browser 512 and/or the secure browser plug-in, and can includecertain elements or features of the client application 404 discussedabove in connection with at least FIG. 4 for example. For instance, theclient agent 514 can include a remote session agent 416 for renderingthe network application at the web browser 512. In some embodiments, thenetwork application is rendered at the hosted secure browser, and therendered data is conveyed or mirrored to the secure browser plug-in 516and/or the client agent 514 for processing and/or display.

By way of an example, a user may be working remotely and may want toaccess a network application that is internal to a secure corporatenetwork while the user is working on a computing device connected to anunsecure network. In this case, the user may be utilizing the standardbrowser 512 executing in the first network 510, in which the firstnetwork 510 may comprise an unsecure network. The server 430 that theuser wants to access may be on the second network 530, in which thesecond network 530 comprises a secure corporate network for instance.The user might not be able to access the server 430 from the unsecurefirst network 510 by clicking on an internal uniform record locator(URL) for the secure website 532. That is, the user may need to utilizea different URL (e.g., an external URL) while executing the standardbrowser 512 from the external unsecure network 510. The external URL maybe directed to or may address one or more hosted web browsers 522configured to access server(s) 430 within the second network 530 (e.g.,secure network). To maintain secure access, the secure browser plug-in516 may redirect an internal URL to an external URL for a hosted securebrowser.

The secure browser plug-in 516 may be able to implement networkdetection in order to identify whether or not to redirect internal URLsto external URLs. The standard browser 512 may receive a requestcomprising an internal URL for a website executing within the securenetwork. For example, the standard browser 512 may receive the requestin response to a user entering a web address (e.g., for secure website532) in the standard browser. The secure browser plug-in 516 mayredirect the user web browser application 512 from the internal URL toan external URL for a hosted web browser application. For example, thesecure browser plug-in 516 may replace the internal URL with an externalURL for the hosted web browser application 522 executing within thesecure network 530.

The secure browser plug-in 516 may allow the client agent 514 to beconnected to the hosted web browser application 522. The client agent514 may comprise a plug-in component, such as an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the standard browser 512. For example,the client agent 514 may comprise an ActiveX control loaded and run by astandard browser 512, such as in the memory space or context of the userweb browser application 512. The client agent 514 may be pre-configuredto present the content of the hosted web browser application 522 withinthe user web browser application 512.

The client agent 514 may connect to a server or the cloud/hosted webbrowser service 520 using a thin-client or remote-display protocol topresent display output generated by the hosted web browser application522 executing on the service 520. The thin-client or remote-displayprotocol can be any one of the following non-exhaustive list ofprotocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

The hosted web browser application 522 may navigate to the requestednetwork application in full-screen mode, and can render the requestednetwork application. The client agent 514 may present the content orrendition of the network application on the web browser application 512in a seamless and transparent manner such that it appears that thecontent is being displayed by the standard browser 512, e.g., based onthe content being displayed in full screen mode. In other words, theuser may be given the impression that the web site content is displayedby the user web browser application 512 and not by the hosted webbrowser application 522. The client agent 514 may transmit navigationcommands generated by the user web browser application 512 to the hostedweb browser application 522 using the thin-client or remote-displayprotocol. Changes to the display output of the hosted web browserapplication 522, due to the navigation commands, may be reflected in theuser web browser application 512 by the client agent 514, giving theimpression to the user that the navigation commands were executed by theuser web browser application 512.

Referring again to FIG. 5, and in operation (4), a new browser tab canopen on the standard browser, to render or display the secure browsersession. The new browser tab can be established or opened by the securebrowser plug-in for instance. The secure browser plug-in and/or a clientagent can receive data from the secure browser session, and can renderthe network application within the new browser tab as discussed above inconnection with FIG. 6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

FIG. 7 depicts another example embodiment of a system of using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and the client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 5. A client application with embedded browser is not available inthe client device 402. A standard or typical (e.g., HTML5) browser isavailable on the client device, from which a user can initiate a requestto access a non-sanctioned network application. A network applicationcan be specified as being sanctioned or non-sanctioned via policies thatcan be set by an administrator or automatically (e.g., via artificialintelligence).

In operation (1), the user may attempt to log into a non-sanctionednetwork application using the standard browser. The user may attempt toaccess a webpage of a server that provisions the network application,and to initiate a request to access the network application. In someembodiments, the request can be forwarded to or intercepted by adesignated gateway service (e.g., in a data path of the request). Forexample, the gateway service (sometimes referred to as SWG) can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. The gatewayservice can detect or otherwise determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB.

In operation (2), the gateway service detects that the requested networkapplication is a non-sanctioned network application. The gateway servicecan for instance extract information from the request (e.g., destinationaddress, name of the requested network application), and compare theinformation against that from a database of sanctioned and/ornon-sanctioned network applications. The gateway service can determine,based on the comparison, that the requested network application is anon-sanctioned network application.

In operation (3), responsive to the determination, the gateway servicecan block access to the requested network application, e.g., by blockingthe request. The gateway service can generate and/or send a URL redirectmessage to the standard browser, responsive to the determination. TheURL redirect message can be similar to a URL redirect message sent fromthe server to the standard browser in FIG. 5 in operation (3). A securebrowser plug-in of the standard browser can receive the URL redirectmessage, and can for example send a request to access the non-sanctionednetwork application, to the secure browser 420. The secure browser 420can direct the request to the server of the non-sanctioned networkapplication.

The server of the non-sanctioned network application may authenticatethe user via the access gateway of the cloud services 408, e.g.,responsive to receiving the request from the secure browser. The servermay communicate with the access gateway to authenticate the user, inresponse to the request. The server may send a request to the accessgateway to authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430. Upon authentication, the secure browser (or acorresponding CEB) can establish a secured connection and an applicationsession with the server.

In operation (4), a new browser tab can open on the standard browser, torender or display the secure browser's application session. The newbrowser tab can be established or opened by the secure browser plug-infor instance. The secure browser plug-in and/or a client agent canreceive data from the secure browser session, and can render the networkapplication within the new browser tab as discussed above in connectionwith FIGS. 5-6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

In some embodiments, in the absence or non-availability of a CEB on theclient device, browser redirection is performed so that each requestednetwork application is accessed via a corresponding hosted securebrowser (or hosted CEB) for handling, instead of having all trafficredirected through a single hosted secure browser (or hosted CEB). Eachdedicated secure browser can provide compartmentalization and improvedsecurity.

The use of a CEB, whether hosted or local to the client device, canallow for end-to-end visibility of application traffic for analytics,service level agreement (SLA), resource utilization, audit, and so on.In addition to such visibility, the CEB can be configured with policiesfor managing and controlling any of these as well as other aspects. Forexample, DLP features can be supported, to control “copy and paste”activities, download of files, sharing of files, and to implementwatermarking for instance. As another example, the CEB can be configuredwith policies for managing and controlling access to local drives and/ordevice resources such as peripherals.

Referring now to FIG. 8, an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s) is depicted. Anenvironment is shown where different types of client devices 402A, 402Bmay be used (e.g., in a BYOD context), such that one may be locallyequipped with a suitable CEB, and another client device may not have asuitable local CEB installed. In such an environment, systems describedin FIGS. 4, 5 and 7 can be used to support each of the client devicesbased on the availability of a locally installed and suitable CEB.

FIG. 9 depicts an example process flow for using local embeddedbrowser(s) and hosted secured browser(s). The process flow can be usedin the environment described above in FIG. 8, to determine whether anembedded browser or a hosted secured browser should be used for eachclient device to access a network application. For example, in operation901, a HTTP client can attempt to access a web service (e.g., server ofa network application). In operation 903, the web service can redirectthe HTTP client to a gateway service for authentication. In operation905, the gateway service can determine if the HTTP client is a CEB. Ifso, in operation 909, the gateway service can determine if the CEB is asuitable CEB, e.g., capable of enforcing defined application policies.If so, in operation 911, the CEB is allowed access to the web service,and can enforce the defined policies.

If the gateway service determines that the HTTP client is not a CEB, thegateway service can cause a virtualized version of a CEB to beinitialized and hosted on a remote server (e.g., a network device 432 ofcloud services 408), in operation 907. In some embodiments, such ahosted CEB may already be available on a network device 432, and can beselected for use. For example in operation 911, the CEB is allowedaccess to the web service, and can enforce the defined policies.

If the gateway service determines that the HTTP client is a CEB, butthat the CEB is not a suitable CEB, the gateway service can cause avirtualized version of a CEB to be initialized and hosted on a remoteserver (e.g., a network device 432 of cloud services 408), in operation907. In some embodiments, such a hosted CEB may already be available ona network device 432, and can be selected for use. For example inoperation 911, the CEB is allowed access to the web service, and canenforce the defined policies.

In some embodiments, if the user is requesting access to a webapplication located in a company data center, the gateway service (incloud service or on premise) can allow access when the clientapplication with CEB is detected. Otherwise, the request can be routedto a service with the hosted virtualized version of the CEB, and thenaccess is authenticated and granted.

At operation 905 and/or operation 909 for instance, the decisions madeon whether the HTTP client is a CEB and whether it is a suitable CEB maybe determined by a number of factors. For example, to determine if theHTTP client is CEB, the gateway service may take into account factors,for example including at least one of: user Identity and strength ofauthentication, client Location, client IP Address, how trusted the useridentity, client location, client IP are, jailbreak status of the clientdevice, status of anti-malware software, compliance to corporate policyof the client device, and/or remote attestation or other evidence ofintegrity of the client software.

To determine if the CEB is able to honor or support all definedapplication policies (which may vary by client version, client OSplatform and other factors), the client device's software and gatewayservice may perform capability negotiation and/or exchange versioninformation. In some embodiments, the gateway service can query or checka version number or identifier of the CEB to determine if the CEB is asuitable CEB to use.

Driving all the traffic though the CEB then allows additional control ofcontent accessing SaaS and Web based systems. Data Loss Prevention (DLP)of SaaS and Web traffic can be applied through the CEB app with featuresincluding copy and paste control to other CEB access applications or ITmanaged devices. DLP can also be enforced by enabling content to bedownloaded only to designated file servers or services under IT control.

Referring now to FIG. 10, depicted is an example embodiment of a systemfor managing user access to webpages. Some webpages (or websites) areknown to be safe while others may be suspect. A user may access awebpage via a corresponding URL through a standard browser. For example,the user may click on a link corresponding to the URL, which may beincluded in an email being viewed using a mail application. An accessgateway (SWG) may intercept an access request generated by the clickingof the link, and can determine if the corresponding URL is safe orsuspect. If the URL is known to be safe, the access gateway can allowthe request to proceed to the corresponding website or web server. Ifthe URL is suspect, the access gateway can redirect the request to behandled via a hosted secure browser. The secure browser can requestaccess for, and access the webpage (on behalf of the standard browser),and can allow the webpage information to be conveyed to the standardbrowser, similar to the handling of a network application via browserredirection as discussed in connection with at least FIGS. 7 and 5.

C. Systems and Methods for Providing a Preview for a Link in a NetworkApplication

The present disclosure is directed towards systems and methods forproviding a preview for a link in a network application. An embeddedbrowser within a client application can provide a mechanism andinterface for users to preview links provided in a network application'ssession (sometimes referred as an HDX session or provisioning session).The network application may be accessed via the client application andthe embedded browser can render a user interface of the networkapplication. A user may click (or otherwise act on) a link (e.g., linkedtext or icon) that is presented within the user interface of the networkapplication. The embedded browser may detect a user action on the link.In some embodiments, when the embedded browser detects the user action,the embedded browser may provide the user an option to open the link inthe embedded browser, for instance in addition to or instead ofinitiating a preview for the link. For instance, when the user acts uponthe link, the user can be provided with an option (e.g., via a selectionmenu) to see a preview or open the link in the embedded browser. If theuser selects the option to see a preview, the embedded browser mayprovide a preview of the link to the user (e.g., in a preview region ofthe embedded browser for the client application).

In some embodiments, a secure web gateway (also referred to herein as asecurity gateway) in communication with the embedded browser may apply auniform resource locator (URL) policy (also referred to herein as apolicy or rule) to the link, for determining whether the embeddedbrowser is allowed to provide the preview. In certain embodiments, theembedded browser can access and apply one or more policies locally onthe client device, to determine if a preview for the link is allowed. Ifallowed, the embedded browser may render, establish, display orotherwise provide a preview for the link (e.g., web link) within apreview region of the network application. The user can for instanceread, zoom (or resize), scroll, or perform some other operation on thepreview. Additionally, the user may close the preview to return to thenetwork application, save the link as a bookmark, and/or open the linkusing a published application (also referred to herein as an HDXapplication or a network application).

In some embodiments, the user may save the link to a ShareFile serviceor application (also referred to herein as a file-sharing application),as a saved weblink for example. One or more servers (also referred to asCitrix workspace server(s)) in communication with the client device maycall the file-sharing application and provide an authentication tokenfrom the embedded browser (e.g., the same authentication token foraccessing the file-sharing application to save the link, or foraccessing the network application) to access the saved weblink. Thus,the user may access a saved weblink at a later time on the file-sharingapplication through the server (or directly through the file-sharingapplication) by providing the authentication token.

When a user operating a client device in a remote environment selects alink within a network or local application (such as an email applicationlike Microsoft Outlook), the page corresponding to the link opens in adefault browser that is separate from the network or local application.The page may open in a new window or one different from that having thelink. However, most users may not prefer to open such a page in a newwindow. If a user is sufficiently interested enough in the page, theuser can open the link (in a new window or a tab) and read the page indetail. Because selecting the link opens a new window or a tab inside adefault browser for instance, users may avoid (or delay) selecting thelink and, as a result, miss the corresponding information contained inthe page. Such a delay or avoidance may negatively affect theproductivity of the user as well as the overall user experience.Additionally, opening several links in a local or remote browserconsumes resources (e.g., overall server or computing resources),potentially consumes user or software licenses, and/or impacts userproductivity.

Referring to FIG. 11, depicted is a block diagram of one embodiment of asystem 1100 for providing a preview of a link in an embedded browser.The system 1100 may include one or more servers 1102, a security gateway1120 with one or more policies 1122, and/or a client device 1104. Theclient device 1104 may execute (e.g., via one or more of the processorsdescribed above in connection with FIG. 1) a client application 1106that includes an embedded browser 1108. The embedded browser 1108 caninclude a preview engine 1116, and can provide a preview region 1118.The embedded browser 1108 can render information/elements of a networkapplication 1110′ that is accessed via the client application 1106, suchas a user interface 1114 of the network application including a link1112. As shall be described in detail below, a preview of the link 1112may be rendered by the preview engine 1116 within the preview region1118. In some instances, the link 1112 may be sent to a file-sharingapplication 1124 for subsequent access by the user at a later time.

In some embodiments, the client application 1106 may include one or moreelements of any embodiment of the client application 404 described abovein connection with at least FIGS. 4 and 8. The client application 1106with the embedded browser 1108 (CEB) can include any element orembodiment of a CEB as previously described above in connection with atleast FIGS. 4 and 8. The embedded browser 1108 may be integrated withinthe client application 1106, as described above. In some embodiments,the client application 1106 may execute on a client device 1104 operatedby a user. The client device 1104 may include one or more elements ofany embodiment of the client device 402 described above in connectionwith at least FIGS. 4, 5, 7, and 8. The network application 1100 mayinclude any type or form of network application 406 described above inconnection with at least FIGS. 2-5, 7, and 8.

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 1100 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the client device 1104, server 1102 and/or security gateway1120 for instance. The hardware includes circuitry such as one or moreprocessors in one or more embodiments.

The embedded browser 1108 of the client application 1106 may be designedor implemented to display a user interface 1114 of the networkapplication 1110, and/or one or more links 1112 within the userinterface 1114. The network application(s) 1110′ may be hosted, run orotherwise executed on the server(s) 1102. The embedded browser 1108 ofthe client application 1106 may include an icon corresponding to orrepresenting the network application 1110′. Upon a user selecting aparticular network application 1110′ (e.g., by selecting a correspondingicon available via the client application 1106), the network application1110′ may be accessed (e.g., as network application 1110) via theembedded browser 1108 of the client application 1106.

In some embodiments, network application 1110′ refers to a networkapplication hosted remotely on server(s) 1102, whereas networkapplication 1110 refers to the network application 1110′ as provisionedto the client application 1106 via a provisioning session (e.g.,established using Citrix high definition user experience (HDX) orindependent computing architecture (ICA) protocol, or remote desktopprotocol (RDP)), and/or a local rendering of the network application onthe client device 1104. The network application 1110′ can be hosted onone or more servers and can have a user interface provisioned to theembedded browser 1108 via a provisioning or delivery session establishedwith the one or more servers 1102. For instance, a virtual deliveryagent (such as the remote session agent described above in reference toat least FIGS. 4 and 8), may establish a connection between theserver(s) 1102 and the client device 1104. The virtual delivery agentmay support a remoting protocol (e.g., HDX or ICA). The virtual deliveryagent may establish the provisioning or delivery session in accordancewith any type or form of protocols, such as RDP, Appliance Link Protocol(ALP), Remote Frame Buffer (RFB) Protocol, and ICA Protocol. Suchprotocols can allow user interface (UI) elements of an application ordesktop session natively hosted on the one or more servers, to begenerated at the one or more servers, and then encoded within using suchprotocols to be delivered or provisioned to a client device remotelylocated from the one or more servers. Hence, the user interface elementscan be reproduced, synchronized and/or mirrored at the client device. Insome embodiments, the virtual delivery agent can establish theprovisioning or delivery session for a user of the client device 1104 toaccess the network application 1110′. The virtual delivery agent canestablish the provisioning or delivery session within or over a secureconnection (e.g., a VPN) established by the networking agent 412 (ofFIGS. 4 and 8) for instance.

In some embodiments, the network application 1110 excludes a web page ora server-side HTML web application delivered via hypertext mark-uplanguage (HTML) to a client device. In some embodiments, the networkapplication 1110 excludes JavaScript generation widgets (AJAX) and/orservice-oriented single-page web applications (e.g., Web 2.0, HTML5applications). The network application 1110′ can include, for example,Microsoft Windows 365 applications such as Outlook, PowerPoint, Word,Excel, and so on. The network application 1110′ can include, forexample, Citrix SharePoint, OneNote, Dropbox, and so on. In each ofthese examples, the user may access the network application 1110′ byselecting or activating the corresponding application icon available onthe client application 1106, and the network application 1110′ hosted onserver(s) 1102 may be remotely provisioned to the client device 1104.

In some embodiments, the network application 1110′ may have anauthentication procedure for authenticating users prior to allowing theuser to access the network application 1110 via the embedded browser1108. The user may provide an authentication token (e.g., by signing in,providing a password or passcode) to the network application 1110′. Thenetwork application 1110′ may verify the authentication token bycomparing the authentication token to authorized users who may accessthe network application 1110′. When the identity of the user is verified(e.g., via the authentication token), the network application 1110 maybe accessed, provisioned and/or rendered on the embedded browser 1108.

In some embodiments, the network application 1110 presented, provisionedor provided via the embedded browser 1108 may have a link 1112 includedon a user interface 1114 of the network application 1110. The userinterface 1114 may be an interface (e.g., graphical user interface (GUI)which provides for interaction, communication and/or other exchange ofinformation between the user and the network application 1110′. Forinstance, the user interface 1114 may include, display or present links,text, buttons, sliding bars, etc.

In some embodiments, the user interface 1114 may include the link 1112.The link 1112 may be a link which is addressed to an internet webpage(e.g., a weblink), a link which is addressed to an internal orexternal/downloadable file, a link to a different portion of the samepage which is displayed on the embedded browser 1108, etc. The link 1112may be a link for accessing any type or form of resource or content(e.g., a web application, a widget, a video file, a picture, ormultimedia file). In each of these instances, the link 1112 may operateto preview or display a page, content or other resource that isdifferent than the page currently being displayed on the embeddedbrowser 1108 when selected, hovered over, or otherwise acted upon by auser.

The embedded browser 1108 may include a preview engine 1118. The previewengine 1118 of the embedded browser 1108 may be designed or implementedto detect, monitor, register, or otherwise identify (generally referredto hereinafter as “identify”) a user action on the link 1112 displayedin the embedded browser 1108 (e.g., detect or identify the occurrence ofthe user action). The preview engine 1118 can include logic or processesfor identifying, detecting, monitoring for, and/or responding to apredetermined or predefined user action for initiating, triggering,generating, producing or otherwise causing a preview for a link 1112.The user may provide or perform user actions to interact with thenetwork application 1110 by selecting buttons, sliding bars, text, thelink 1112, etc. The embedded browser 1108 may identify these useractions. For instance, the embedded browser 1108 may include a DocumentObject Model (DOM) event listener which registers DOM events (such asmouse DOM events, keyboard DOM events, HTML frame/object/form DOMevents, and/or other user interface DOM events). The DOM event listenermay register these DOM events when they occur within the user interface1114. The embedded browser 1108 may identify the user actions based onthe registered DOM events within the user interface 1114. In someinstances, the user may select, hover over, or otherwise perform apredefined, specific or predetermined user action on the link 1112, toinitiate or trigger a preview for the link 1112. For instance, the usermay select or hover over the link 1112 to preview the page correspondingto the link 1112. The embedded browser 1108 may identify the user actionon the link 1112.

The preview engine 1116 of the embedded browser 1108 may be designed orimplemented to establish, display, render, generate, present orotherwise provide a preview of the link 1112. The preview may be atleast a portion of the page which is provided to the user upon the link1112 being opened by the user. In some embodiments, the preview mayinclude the whole page which is provided to the user when the link 1112is opened. In other embodiments, the preview may be less than the wholepage that is provided to the user when the link 1112 is opened (e.g.,just the text of the page, an upper portion of the page). For example,the preview engine may initiate a partial retrieval of the pageassociated with the link 1112. The partial retrieval may be a summary orsnippet of the page. The preview engine 1116 may retrieve the previewfrom cached data or directly from the source of the link 1112. Forinstance, the preview engine 1116 may access data from the pageassociated with the link 1112 and provide the data to the user in apreview format (rather than opening the link 1112 in a new page or taboutside of the embedded browser 1108). The user may then view thepreview within the embedded browser 1108.

The preview engine 1116 may render the preview in a preview region 1118of the embedded browser 1108. The preview region 1118 may be a portionof the embedded browser 1108 within which the preview is rendered. Forinstance, the preview region 1118 may be a new browser window or tab forthe embedded browser 1108. As another example, the preview region 1118may be a pop-up window, call-out or overlay, within the same window ordisplayed portion of the embedded browser 1108. The pop-up window orpreview region may overlay the current window (e.g., covering a portionof the embedded browser 1108). Additionally, the pop-up window orpreview region may be a designated portion of the current window of theembedded browser 1108, which is not in use when the preview is initiatedby the user for instance. As another example, the window of the embeddedbrowser 1108 may be expanded (e.g., to have an increased window size) toaccommodate for the pop-up window within the same window of the embeddedbrowser 1108. In this example, various portions of the user interface1114 may be shifted to accommodate for the pop-up window. For instance,the window may expand to a larger size with the user interface 1114being shifted to the left side of the window, and the pop-up windowincluding the preview may be rendered within the right side of thewindow.

In some embodiments, the preview region 1118 may render the preview whenthe user action on the link 1112 is identified. For instance, thepreview region 1118 may be defaulted to render a portion of the userinterface 1114 of the network application 1110, and may render thepreview when the user action on the link 1112 is identified. In thisregard, the preview region 1118 may selectively render the preview orthe user interface 1114 according to user actions on the link 1112.

In some embodiments, the preview engine 1116 may establish, generateand/or configure the preview region 1118 of the embedded browser 1108.For instance, the preview engine 1116 may establish, generate and/orconfigure the preview region 1118 when the embedded browser 1108identifies, recognizes or detects the user action on the link 1112.

In some embodiments, the preview engine 1116 may establish a location ofthe preview region 1118. The preview region 1118 may correspond to, orinclude a static and/or designated location within the embedded browser1108 (e.g., the preview region 1118 is located in the same locationwhenever a user action on any link 1112 is identified). Additionally,the preview region 1118 may have a dynamic location, shape, look and/ordimensions within or relative to the embedded browser 1108. The previewregion 1118 can be restricted within a displayed or defined boundary ofthe embedded browser 1108 (e.g., within the current window or a boundaryof the embedded browser 1108), or can extend or be located beyond theboundary (e.g., the preview region 1118 may extend partially within andpartially outside of the current window, or the preview region 1118 mayextend wholly outside the current window). In some embodiments, thelocation of the preview region 1118 may change according to variousinputs. For instance, the location of the preview region 1118 may changedepending on a location of the link 1112 within the user interface 1112.As one example, where the link 1112 is located near the bottomright-hand side of the user interface 1112, the preview region 1118 maybe located near the center right-hand side of the embedded browser 1108.As another example, where the link 1112 is located in the centerright-hand side of the embedded browser 1108, the preview region 1118may be located near the bottom left-hand side of the embedded browser1108.

In some embodiments, the preview engine 1116 may establish contentsand/or elements (e.g., graphical elements) of the preview region 1118.For instance, the preview region 1118 may correspond to or include awindow or tab of the embedded browser 1108. In some embodiments, theembedded browser 1108 of the client application 1106 may be designed orimplemented to retrieve, open or otherwise access (hereafter generallyreferred to as “access”) a page of the link 1112. The preview engine1116 may access an address (e.g., URL or IP address) associated with thelink 1112 to identify or access the page associated with the link 1112.For instance, the preview engine 1116 of the embedded browser 1108 mayaccess the page of the link responsive to a user action on the link 1112via the network application 1110. The preview engine 1116 may render atleast some contents of the page within preview region 1118.

In the embodiments described herein, the preview engine 1116 may renderthe preview within the preview region 1118 of the same embedded browser1108 which is currently operated, controlled, or otherwise used by theuser. Accordingly, the embedded browser 1108, which is already openedand has memory allocated thereto, can provide the preview to the userquicker and more efficiently than instances where the link 1112 isopened in a new or different browser. For instance, rather thancommunicating instructions to a new browser to open the link 1112, theembedded browser 1118 can render the preview directly to the user. As aresult, latencies and lag times for opening the new browser, opening thelink 1112, allocating resources such as memory, and accessing thecorresponding page are decreased. Such decreased latencies and lag timesresult in an improved user experience. Furthermore, providing thepreview within the embedded browser 1108 provides the user with the samelook and feel (rather than opening a new browser which may have adifferent interface). The user can operate within the same environment(e.g., the embedded browser 1108) and seamlessly access the link of thenetwork application 1110 and its user interface 1114. Each of theseaspects may result in an improved user experience and convenience, asopposed to opening the link 1112 in a different (e.g., new) browser orexternal application. As a result of the improved user experience, usersmay be less likely to avoid or delay selecting the link 1112 andtherefore be less likely to miss the corresponding information containedin the page. Therefore, the user may benefit from increasedproductivity.

In some embodiments, the preview engine 1116 may be designed orimplemented to enable user manipulation, action(s) or operation(s) onthe preview within the preview region 1118. For instance, the user mayscroll, zoom (e.g., resize), terminate, and/or provide other useractions on the preview within the preview region 1118. The embeddedbrowser 1108 may identify the user actions and control or update thepreview according to the detected user actions. The embedded browser1108 may identify the user actions within the preview in a mannersimilar to the embedded browser 1108 identifying user actions describedabove. As one example, the user may provide a user action to scroll thepreview within the preview region. The embedded browser 1108 mayidentify a scrolling DOM event within the preview region 1118. Thepreview engine 1116 may change, adjust or update the portion of the pagecorresponding to the link 1112 which displayed within the preview region1118 in accordance with the scrolling DOM event. As another example, theembedded browser 1108 may identify a resizing DOM event within thepreview region 1118. The preview engine 1116 may change the size of thepreview region 1118 (and/or the preview) in accordance with the resizingDOM event. As still another example, the embedded browser 1108 mayidentify a termination DOM event within the preview region 1118. Thepreview engine 1116 may close the preview region 1118 (e.g., tab orsub-window) of the embedded browser 1108. The preview engine 1116 maydisplay or restore the user interface 1114 of the network application1110 where the preview region 1118 was previously located. In thisregard, the user may return (e.g., efficiently or conveniently) to thenetwork application 1110 following the user closing the preview (e.g.,via providing the termination DOM event within the preview region 1118).

In some embodiments, the preview engine 1116 may be designed orimplemented to present an option to preview or open the link via thenetwork application 1110. For instance, the preview engine 1116 may beconfigured to identify or detect different predefined user action on thelink 1112 corresponding to each option. The preview engine 1116 maydisplay options to open the preview (e.g., as described above) or openthe page corresponding to the link 1112 via the network application1110. The preview engine 1116 may present or identify one or more otheruser actions (e.g., on the options). The user may select (e.g., byclicking on) the desired option. The preview engine 1116 may identifythe DOM event associated with the click on the desired option. Thepreview engine 1116 may execute the option according to the userselection (e.g., render the preview in the preview region 1118 asdescribed above, or open the link and render the page in the networkapplication 1110′).

In some embodiments, the preview engine 1116 may communicate with orinteroperate with a security gateway 1120. The security gateway 1120 maybe designed or implemented to perform policy-based access control forfiltering links for preview, for example. The security gateway 1120 can,for instance, apply a policy 1122 on the link 1112 to determine if theembedded browser 1108 is allowed to provide the preview. In someembodiments, the security gateway 1120 may retrieve the policy 1122 froma policy store and apply the retrieved policy 1122 on the link 1112.Additionally, the security gateway 1120 may store the policy 1122locally on the security gateway 1120. In still other embodiments, theembedded browser 1108 (rather than the security gateway 1120) may accessthe policy 1122 (e.g., via a policy store or a locally-stored policy)and apply the policy 1122 to the link 1112.

The security gateway 1120 (and/or the embedded browser 1108) may performthe policy-based access control prior to the preview engine 1116rendering the preview (or opening the link), and/or prior to detectingthe user action. The security gateway 1120 (and/or the embedded browser1108) may apply the policy before any pages associated with the link areaccessed by any of the components described herein. The security gateway1120 (and/or the embedded browser 1108) may apply the policy 1122 as aprotection and security measure. The security gateway 1120 (and/or theembedded browser 1108) may use the policy 1122 to identify variousidentifiers, aspects or characteristics of the page (e.g., URL, address,domain name, security settings). The policy 1122 may list, recite,classify, or otherwise identify sanctioned and/or unsanctioned pages orapplications. For instance, a list of sanctioned pages and applicationsmay be preconfigured, customizable, etc.

The security gateway 1120 may identify whether the page is a sanctionedpage based on the identifiers, aspects or characteristics of the page.Where the security gateway 1120 (and/or the embedded browser 1108)identifies the page as sanctioned, the security gateway 1120 (and/or theembedded browser 1108) may permit access to the link by the embeddedbrowser 1108 (e.g., by providing an identifier or an indication to theembedded browser 1108 indicating that the embedded browser 1108 isallowed to access the link 1112). If the security gateway 1120 (and/orthe embedded browser 1108) identifies the page as unsanctioned, thesecurity gateway 1120 (and/or the embedded browser 1108) may deny accessto (e.g., block) the link by the embedded browser 1108. Accordingly, theembedded browser (e.g., the preview engine 1116) may access the page forthe link if the security gateway 1120 (and/or the embedded browser 1108)applies the policy 1122 and determines that the page is sanctioned.

In some embodiments, the system 1100 may include a file-sharingapplication 1124. The file-sharing application 1124 may be designed orimplemented to store links (or files or other pages) for subsequentaccess by the user at a later date. Additionally or alternatively, thefile-sharing application 1124 may be designed or implemented to providethe links (or files or other pages) to other users (e.g., for sharingbetween users) based on a corresponding user action. In this example,the user may select an option to share the link 1112 to another user(for instance, because the user believes the other user may beinterested in the content of the link 1112). The link 1112 may beprovided to the file-sharing application 1124 with credentialsassociated with the other user (e.g., with an email address, user name).The other user may receive an indication which indicates the link 1112has been shared by the user. The other user may provide anauthentication token (e.g., log-in information) to the file-sharingapplication 1124, and may then access the link 1112.

When a user action (e.g., predefined or otherwise) on a link 1112 isdetected, the preview engine 1116 may be designed or implemented topresent an option to preview the link 1112, share the link 1112, or savethe link 1112 (e.g., as a weblink or bookmark), etc. The option may bepresented as part of the user interface 1114. In other embodiments, thepreview within the preview region 1118 may include a mechanism (e.g., abutton or selectable menu) allowing for an option to save or share thelink 1112.

The preview engine 1116 of the embedded browser 1108 may be designed orimplemented to identify a user action to select an option to save (orshare) the link 1112 to the file-sharing application 1124. The embeddedbrowser 1108 may save the link 1112 to the file-sharing application 1124responsive to receiving the selection of the option. The file-sharingapplication 1124 may receive, from the preview engine or the embeddedbrowser, the address associated with the link 1112 and an authenticationtoken associated with the user. The authentication token describedherein may be similar to the authentication token described above forauthenticating users prior to rendering the network application 1110 onthe embedded browser 1108. In some embodiments, the address andauthentication token may be communicated from the preview engine 1116 tothe file-sharing application 1124. In other embodiments, the address andauthentication token may be communicated from (or via) the server 1102(e.g., workspace server) to the file-sharing application 1124.

The user may access the file-sharing application 1124 (e.g., via theclient application 1106, via another device). The user may provide theuser's authentication token to the file-sharing application 1124 and mayselect the saved link 1122. The user may then preview the link (asdescribed above), or open the link using the network application 1110 orthe embedded browser for instance.

Referring to FIG. 12, depicted is a flow diagram of one embodiment of amethod for providing a preview of a link in a network application. Thefunctionalities of the method may be implemented using, or performed by,the components detailed herein in connection with FIGS. 1-11. In briefoverview, a client application can provide access to a networkapplication (1200). An embedded browser can display a link (1205). Theembedded browser can identify a user action on the link (1210). Apreview engine may provide a preview of the link (1215).

Referring now to operation (1200), and in some embodiments, a clientapplication can provide access to a network application. In someembodiments, the client application may be native or installed on aclient device, and may execute on the client device. The clientapplication may provide access to the network application via anembedded browser of the client application. The network application maybe hosted on one or more servers and may have a user interfaceprovisioned to the embedded browser via a provisioning sessionestablished with the one or more servers. In some embodiments, theembedded browser may be integrated within the client application, e.g.,via program code or script insertion. The embedded browser can beintegrated with the client application to ensure that traffic related tothe network application is routed through and/or processed in the clientapplication, which can provide the client application with real-timevisibility to the traffic (e.g., when decrypted through the clientapplication), and user interactions and behavior. For example, theembedded browser can be integrated with the client application toimprove user experience by natively or locally allowing (e.g., using theembedded browser's features) previews of links in the UI of a networkapplication accessed via the client application. The embedded browsercan provide a seamless experience to a user as the network applicationis requested via the user interface (shared by the client applicationand the embedded browser) and rendered through the embedded browserwithin the same user interface. The client application may open,initiate, or otherwise launch the embedded browser when the networkapplication is selected or otherwise accessed by the user. Additionallyor alternatively, the client application may open, initiate, orotherwise launch the embedded browser automatically when the clientapplication is opened by the user.

The user may access the network application by selecting an iconrendered on the embedded browser of the client application. The networkapplication may be installed, executed, hosted and/or located on aserver remote from the client device. The user may provide anauthentication token to the server for accessing the networkapplication. The authentication token may be used for determiningwhether the user is authorized to access the network application. Whenthe user is authorized (as determined by the server), the networkapplication may be accessed via the embedded browser of the clientapplication. In some embodiments, a user interface for the networkapplication may be provisioned and/or rendered on the embedded browser.

In some embodiments, a virtual delivery agent (such as the remotesession agent described above in reference to at least FIGS. 4 and 8)may establish a connection between the servers and the client device.The virtual delivery agent may be embodied within the client applicationand/or the servers. The virtual delivery agent may support a remotingprotocol (e.g., HDX or ICA). The virtual delivery agent may establishthe provisioning or delivery session in accordance to any variety ofprotocols, such as the RDP, ALP, RFB Protocol, and ICA Protocol. In someembodiments, the virtual delivery agent can establish the provisioningor delivery session for a user of the client device to access thenetwork application. The virtual delivery agent can establish theprovisioning or delivery session within or over a secure connection(e.g., a VPN) established by the networking agent 412 (of FIGS. 4 and 8)for instance.

Referring now to operation (1205), and in some embodiments, the embeddedbrowser may display a link. In some embodiments, the embedded browser ofthe client application may display the link within the user interface ofthe network application. The link may be located within the userinterface rendered, displayed or presented on the embedded browser. Thelink may be a link to a webpage (e.g., a weblink), a link to a local ordownloadable page, a portion of the same page currently open in theembedded browser, etc. By way of example, the network application may bean email exchange application (similar to Microsoft Outlook). The linkmay be displayed within an email sent to the user. The link may directthe user to another page (such as a webpage) including various content.In some instances, the link may have different font characteristics(e.g., color, underlined, bolded) than other text within the userinterface. Additionally, the link may incorporate, recite or display anaddress (e.g., a hypertext transfer protocol or secure hypertexttransfer protocol address, for instance). In some embodiments, the linkmay be incorporated in or correspond to an icon. In each of theseinstances, the user may identify the link according to variouscharacteristics of the text.

In some embodiments, the embedded browser (or a security gateway) mayapply various policies to determine whether the link may be previewed bythe user, as shall be discussed in greater detail below. Where a link isnot available for previewing, the link may be displayed in a differentmanner (e.g., in a different color, font, italicized) than links where apreview is available. The user may then distinguish between links wherepreviews are available and links where previews are not available.

Referring now to operation (1210), and in some embodiments, the embeddedbrowser may detect or identify a user action taken or performed on thelink. In some embodiments, a preview engine of the client applicationmay identify a user action (e.g., occurrence or performance of the useraction) on the link displayed on the embedded browser. The previewengine may include a DOM event listener that detects various DOM eventsprovided by a user (e.g., mouse DOM events, keyboard DOM events). TheDOM event listener may identify the DOM events as user actions.Accordingly, the preview engine may identify user action on the linkbased on the corresponding DOM events. The user action may includehovering over the link, selecting (or clicking on) the link, etc.

The preview engine may monitor for specific or predefined user actionson the link. For instance, the preview engine may initiate a preview ofa link when a user hovers over the link, whereas the preview engine mayopen the link when the user selects (e.g., by clicking on) the link. Asanother example, the preview engine may initiate the preview when a userright-clicks on the link, whereas the preview engine may open the linkwhen the user left-clicks on the link. Each of these user actions may bedetected by the preview engine, and the preview engine may performvarious actions or steps in accordance with the detected user actions.

In some embodiments, the preview engine may cause a security gateway toapply a policy on the link to determine if the embedded browser isallowed to provide the preview. In other embodiments, the embeddedbrowser may retrieve a policy (e.g., from a policy store or alocally-stored policy). In these embodiments, the embedded browser mayapply the policy to the link to determine if the embedded browser isallowed to provide the preview. The security gateway (or embeddedbrowser) may use the policy to determine whether the page associatedwith the link is a sanctioned or allowed page (or includes any type orform of allowed content and/or resources). The security gateway (orembedded browser) may identify various characteristics, aspects oridentifiers associated with the link. The policy may include varioussanctioned pages, content, resources, etc. The security gateway (orembedded browser) may determine, based on the identifiers, whether thepage associated with the link fits within the policy (e.g., whether thepage is a sanctioned page, whether the content is sanctioned content,whether the page uses sanctioned resources). In embodiments where thepreview engine causes the security gateway (or embedded browser) toapply the policy on the link, the preview engine may provide the previewof the link responsive to receiving an indication from the securitygateway that the embedded browser is allowed to provide the preview.

In instances where the security gateway or embedded browser determinesthe link may not be previewed (e.g., due to the page/content/resourcesbeing unsanctioned), the preview engine may ignore, disable, deny, blockor otherwise reject the user action. Additionally or alternatively, thepreview engine may cause a pop-up or other indication to be displayedwhich indicates that the preview is not available. In still otherinstances, the preview engine may disable the link such that the link isnot distinguishable from other portions of the user interface (e.g., thesame font characteristics as other text in the user interface), thuspreventing the user from performing or attempting to perform a useraction on the link (e.g., to initiate a preview).

Referring now to operation (1215), and in some embodiments, the previewengine may provide a preview of the link. In some embodiments, thepreview engine of the client application may provide the preview inresponse to the identified user action (e.g., at operation 1210). Thepreview engine may provide the preview by rendering or displaying thepreview in a preview region of the embedded browser.

The preview may be at least a portion of the page which is provided tothe user upon the link being opened by the user. In some embodiments,the preview may include the whole page which is provided to the userwhen the link is opened. In other embodiments, the preview may be lessthan the whole page that is provided to the user when the link is opened(e.g., just the text of the page, an upper portion of the page). Forinstance, the preview engine may initiate a partial retrieval of thepage associated with the link. The partial retrieval may be a summary orsnippet of the page. The preview engine may retrieve the preview fromcached data or directly from the source of the link. For example, thepreview engine may access data from the page associated with the linkand provide the data to the user in a preview format (rather thanopening the link in a new page or tab outside of the embedded browser).The user may then view the preview within the embedded browser. In someembodiments, the preview engine may establish the preview region of theembedded browser. The preview engine may establish the preview regionwhen the preview region identifies the user action on the link (e.g., atoperation 1210). The preview engine may establish a location, shape,size and/or dimensions of the preview region and/or content of thepreview region.

The preview region may be a new browser window or tab for the embeddedbrowser. As another example, the preview region may be a pop-up windowwithin the same window of the embedded browser. The pop-up window orpreview region may be overlaid the current window (e.g., covering aportion of the embedded browser). Additionally, the pop-up window may bea designated portion of the current window of the embedded browser whichis not in use when the preview is initiated by the user. As anotherexample, the window of the embedded browser may be expanded (e.g., tohave an increased window size) to accommodate for the pop-up windowwithin the same window of the embedded browser. In this example, variousportions of the user interface may be shifted to accommodate for thepop-up window. For instance, the window may expand to a larger size withthe user interface being shifted to the left side of the window, and thepop-up window including the preview may be rendered within the rightside of the window. Accordingly, the preview engine may determine wherethe window (or tab, pop-up window, etc.) is to be located within theembedded browser.

In certain embodiments, the preview engine may provide, retrieve,access, select, or establish the content of the preview within thepreview region. The preview engine may access an address (e.g., URL orIP address) associated with the link to identify or access the pageassociated with the link. For instance, the preview engine of theembedded browser may access the page of the link responsive to a useraction on the link via the network application. The preview engine mayrender at least some contents (e.g., cached data, data from the hostserver, data from the source) of the page within preview region.

In some embodiments, the preview engine may perform various actions onthe preview within the preview region, e.g., in response to user actionsperformed on the preview. For instance, the preview engine may scrollthe preview, resize the preview, terminate the preview, etc. The usermay provide user actions within the preview region. The preview enginemay identify the user actions (similar to the manner described above foridentifying user actions). The preview engine may, for instance,identify a user action to scroll the preview within the preview region(e.g., scroll down). The preview engine may then move the portion of thepage previewed in the preview region according to the user action (e.g.,provide a lower portion of the page within the preview region, providesubsequent text in the page within the preview region). Additionally,the preview engine may, for instance, identify a user action to resizethe preview (e.g., enlarge the preview). The preview engine may thenchange the size of the preview region (and correspondingly the size ofthe preview) according to the user action (e.g., enlarge the previewregion with respect to the window of the embedded browser, shrink theembedded browser and expand the preview region). The preview engine maythen provide more content from the page within the preview region. Insome embodiments, the preview engine may provide an increased text sizeof text within the preview region. Additionally, the preview engine may,for instance, identify a user action to terminate the preview. The useraction to terminate the preview may be, for instance, no longer hoveringover the link, selecting a close button associated with terminating thepreview, etc. The preview engine may associate these user actions withterminating the preview. When the preview engine detects these useractions, the preview engine may then close the preview region in theembedded browser. Following terminating the preview, the preview enginemay expand the size of the current window of the embedded browser orotherwise return the current window to normal (e.g., without the previewregion). The user interface of the network application may then returnto the user interface shown at, for instance, operation (1205).

In some embodiments, the embedded browser may access a page for the linkfor rendering within the user interface of the network application. Theembedded browser may access the page in response to a user action toopen the link via the network application. The embedded browser maydistinguish user actions for opening the link via the networkapplication from user actions for previewing the link. For instance, thepreview engine may associate hovering over the link with a user actionto preview the link, and the preview engine may associate selecting(e.g., by clicking on) the link with opening the link. The previewengine may open the link within the network application when the userselects the link, and provide the preview within the preview region whenthe user hovers over the link. In some embodiments, the user may providea user action to open the page prior to previewing the page (e.g., onthe user interface of the network application shown at, for instance,operation 1205)). In this regard, the user may directly open the pagewithout previewing the page. In some embodiments, the user may providethe user action to open the link following the user previewing the linkwithin the preview region. For instance, the preview may include abutton, tab, or other indication or option that permits the user to openthe page with the network application. The preview engine may detect orotherwise register a user action selecting the option to open the linkwith the network application. The preview engine may then open the pagecorresponding to the link within the network application. In anotherexample, the user may terminate the preview (as described above), andselect (e.g., by clicking on) the link to open the link with the networkapplication. The user may open the page via the network applicationfollowing the preview being rendered in the preview region.

In some embodiments, the embedded browser may save the link to afile-sharing application. The file-sharing application may be accessedvia the embedded browser (within the client application of the sameclient device or a different client device). The user may provide a useraction to save the link (for instance, selecting a save link button oroption). The embedded browser may detect or otherwise register the useraction to save the link. The embedded browser may provide for instancean address associated with the link (and an authentication token, suchas log-in information, as user name, etc., associated with the user) tothe file-sharing application. In other embodiments, the address andauthentication token may be communicated from (or via) the server 1102(e.g., workspace server) to the file-sharing application 1124. Thefile-sharing application may save the link with an account, profile,file, etc., associated with the user based on the authentication token.The link may be saved as a weblink or bookmark. The user maysubsequently access the saved link by providing the authentication tokento the file-sharing application. The authentication token may confirmthe identity of the user, according to the provided authenticationtoken. The user may then access links saved by the user. The user maypreview the links (as described above), or open the links using thenetwork application 1110 or the embedded browser for instance.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The systems and methodsdescribed above may be implemented as a method, apparatus or article ofmanufacture using programming and/or engineering techniques to producesoftware, firmware, hardware, or any combination thereof. In addition,the systems and methods described above may be provided as one or morecomputer-readable programs embodied on or in one or more articles ofmanufacture. The term “article of manufacture” as used herein isintended to encompass code or logic accessible from and embedded in oneor more computer-readable devices, firmware, programmable logic, memorydevices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,USB Flash memory, hard disk drive, etc.). The article of manufacture maybe accessible from a file server providing access to thecomputer-readable programs via a network transmission line, wirelesstransmission media, signals propagating through space, radio waves,infrared signals, etc. The article of manufacture may be a flash memorycard or a magnetic tape. The article of manufacture includes hardwarelogic as well as software or programmable code embedded in a computerreadable medium that is executed by a processor. In general, thecomputer-readable programs may be implemented in any programminglanguage, such as LISP, PERL, C, C++, C #, PROLOG, or in any byte codelanguage such as JAVA. The software programs may be stored on or in oneor more articles of manufacture as object code.

While various embodiments of the methods and systems have beendescribed, these embodiments are illustrative and in no way limit thescope of the described methods or systems. Those having skill in therelevant art can effect changes to form and details of the describedmethods and systems without departing from the broadest scope of thedescribed methods and systems. Thus, the scope of the methods andsystems described herein should not be limited by any of theillustrative embodiments and should be defined in accordance with theaccompanying claims and their equivalents.

We claim:
 1. A computer-implemented method comprising: providing anapplication executable on a client device, the application including anembedded browser integrated therein; receiving a request to view apreview of a link provided in a user interface via the embedded browser;identifying a preview of the link, the preview comprising a uniformresource locator to show at least a portion of content accessible viathe link; and displaying the preview in a window of the embeddedbrowser.
 2. The method of claim 1, wherein the embedded browser isconfigured to access via the link content accessible from a remotecomputing device.
 3. The method of claim 1, further comprisingreceiving, by the embedded browser, the request to view the preview ofat least the portion of content accessible via the link provided in theuser interface.
 4. The method of claim 1, further comprising identifyingthe preview based at least on the request.
 5. The method of claim 1,further comprising identifying the preview based at least on one or moreportions of the content accessible via the link or on a description ofthe content.
 6. The method of claim 1, further comprising accessing, bythe embedded browser, the preview corresponding to the link while thelink is being displayed.
 7. The method of claim 1, further comprisingproviding, by the embedded browser, a user interface element to requestto preview the link.
 8. A system comprising: one or more processors,coupled to memory and configured to: provide an application executableon a client device, the application including an embedded browserintegrated therein; receive a request to view a preview of a linkprovided in a user interface via the embedded browser; identify apreview of the link, the preview comprising a uniform resource locatorto show at least a portion of content accessible via the link; anddisplay the preview in a window of the embedded browser.
 9. The systemof claim 8, wherein the embedded browser is further configured to accessvia the link content accessible from a remote computing device.
 10. Thesystem of claim 8, wherein the one or more processors are furtherconfigured to receive the request to view the preview of at least theportion of content accessible via the link provided in the userinterface.
 11. The system of claim 8, wherein the one or more processorsare further configured to identify the preview based at least on therequest.
 12. The system of claim 8, wherein the one or more processorsare further configured to identify the preview based at least on one ormore portions of the content accessible via the link or on a descriptionof the content.
 13. The system of claim 8, wherein the one or moreprocessors are further configured to access the preview corresponding tothe link while the link is being displayed.
 14. The system of claim 8,wherein the one or more processors are further configured to provide auser interface element to request to preview the link.
 15. Anon-transitory computer-readable medium comprising processor-executableinstructions that when executed by one or more processors, cause the oneor more processors to: provide an application executable on a clientdevice, the application including an embedded browser integratedtherein; receive a request to view a preview of a link provided in auser interface via the embedded browser; identify a preview of the link,the preview comprising a uniform resource locator to show at least aportion of content accessible via the link; and display the preview in awindow of the embedded browser.
 16. The computer-readable medium ofclaim 15, further comprising instructions that cause the one or moreprocessors to access via the link content accessible from a remotecomputing device.
 17. The computer-readable medium of claim 15, furthercomprising instructions that cause the one or more processors to receivethe request to view the preview of at least the portion of contentaccessible via the link provided in the user interface.
 18. Thecomputer-readable medium of claim 15, further comprising instructionsthat cause the one or more processors to identify the preview based atleast on the request.
 19. The computer-readable medium of claim 15,further comprising instructions that cause the one or more processors toidentify the preview based at least on one or more portions of thecontent accessible via the link or on a description of the content. 20.The computer-readable medium of claim 15, further comprisinginstructions that cause the one or more processors to access the previewcorresponding to the link while the link is being displayed.